lep pod
Manages pods on the DGX Cloud Lepton.
A Pod (short for "DGX Cloud Lepton Pod") is a container runtime that allows you to run interactive sessions on the DGX Cloud Lepton. Think of it as a remote server that you can access via SSH, and use it as a remote development environment. You can use it to run Jupyter notebooks, or to run a terminal session, similar to a cloud VM but much more lightweight.
Usage
lep pod [OPTIONS] COMMAND [ARGS]...
Options
--help: Show this message and exit.
Commands
create: Creates a pod with the given resource shape, mount, env and...get: Show pod detail and optionally save its spec JSON.list: Lists all pods in the current workspace.remove: Removes a pod.ssh: SSH into a running pod.
lep pod create
Creates a pod with the given resource shape, mount, env and secret.
Usage
lep pod create [OPTIONS]
Options
-n,--name TEXT: Name of the pod to create. [required]-f,--file FILE: If provided, load the pod spec from this JSON file before applying CLI overrides. The file could be generated by UI → CLI → 'Use spec file', or by running: pod get -i [pod_id] --path [download_path]`.--resource-shape TEXT: Resource shape for the pod. Available types are: 'cpu.small', 'cpu.medium', 'cpu.large', 'gpu.a10', 'gpu.a10.6xlarge', 'gpu.a100-40gb', 'gpu.2xa100-40gb', 'gpu.4xa100-40gb', 'gpu.8xa100-40gb', 'gpu.a100-80gb', 'gpu.2xa100-80gb', 'gpu.4xa100-80gb', 'gpu.8xa100-80gb', 'gpu.h100-sxm', 'gpu.2xh100-sxm', 'gpu.4xh100-sxm', 'gpu.8xh100-sxm'.--mount TEXT: Persistent storage to be mounted to the deployment, in the formatSTORAGE_PATH:MOUNT_PATH.-e,--env TEXT: Environment variables to pass to the deployment, in the formatNAME=VALUE.-s,--secret TEXT: Secrets to pass to the deployment, in the formatNAME=SECRET_NAME. If secret name is also the environment variable name, you can omit it and simply passSECRET_NAME.--image-pull-secrets TEXT: Secrets to use for pulling images.-ng,--node-group TEXT: Node group for the pod. If not set, use on-demand resources. You can repeat this flag multiple times to choose multiple node groups. Multiple node group option is currently not supported but coming soon for enterprise users. Only the first node group will be set if you input multiple node groups at this time.--container-image TEXT: Container image to run.--container-command TEXT: Command to run in the container.-lg,--log-collection BOOLEAN: Enable or disable log collection (true/false). If not provided, the workspace setting will be used.-ni,--node-id TEXT: Node for the pod. You can repeat this flag multiple times to choose multiple nodes. Please specify the node group when you are using this option-qp,--queue-priority TEXT: Set the priority for this pod (dedicated node groups only).-cbp,--can-be-preempted: Allow this pod to be preempted by higher priority workloads.-cp,--can-preempt: Allow this pod to preempt lower priority workloads.--container-port TEXT: Container ports to expose. Format: [port]:[protocol]:[strategy][:strategy]. [port] : 1-65535 [protocol] : tcp | udp | sctp [strategy] : proxy | hostmap - hostmap: host port (random 40000-65535) mapped on node IP - proxy : generate public URL; only ONE port can enable proxy
Examples: 8080:tcp:proxy -> proxy only 8080:udp:hostmap -> host mapping only 8080:tcp:proxy:hostmap -> both strategies (note: only first proxy will take effect)
Notice: Exposing container ports may increase your service's security risk. Please implement appropriate authentication and security controls; you are solely responsible for the security of any services exposed.
--with-reservation TEXT: Assign the pod to a specific reserved compute resource using a reservation ID (only applicable to dedicated node groups).--allow-burst-to-other-reservation: If set, the pod can temporarily use free resources from nodes reserved by other reservations. Be aware that when a new workload bound to those reservations starts, your pod may be evicted.--help: Show this message and exit.
lep pod get
Show pod detail and optionally save its spec JSON.
Usage
lep pod get [OPTIONS]
Options
-n,--name TEXT: Pod name [required]-p,--path PATH: Optional local path to save the pod spec JSON. Directory or full filename accepted. If a directory is provided, the file will be saved as pod-spec-[name].json.--help: Show this message and exit.
lep pod list
Lists all pods in the current workspace.
Usage
lep pod list [OPTIONS]
Options
-p,--pattern TEXT: Regular expression pattern to filter pod names.--help: Show this message and exit.
lep pod remove
Removes a pod.
Usage
lep pod remove [OPTIONS]
Options
-n,--name TEXT: The pod name to remove. [required]--help: Show this message and exit.
lep pod ssh
SSH into a running pod.
Usage
lep pod ssh [OPTIONS]
Options
-n,--name TEXT: The pod name to ssh. [required]--help: Show this message and exit.