lium describe
One pod in full — ports, GPU, template, access, billing — as a single manifest.
lium describe POD_ID [OPTIONS]
Arguments
POD_ID— Pod name, huid, or id. Unlike the pod-targeting commands, this one does not take the numeric index fromlium ps.
Options
| Flag | Effect |
|---|---|
--json | Print the manifest as machine-readable JSON |
Examples
lium describe my-pod
lium describe my-pod --json | jq '.ports.ssh_external'
--json carries the whole manifest, grouped into pod, gpu, machine,
ports, access, template, storage, and billing. The default table is the
readable subset of it — pod, GPU, machine, template, ports, SSH and cost — so
fields like pod id, creation time, location, Jupyter URL and volume encryption
are only in the JSON.
Both outputs spell out the port direction, the detail that costs the most time to
get wrong: the JSON mapping reads internal -> external and carries that
direction as a field, while the table column is labelled ext→int. The SSH port
is broken out from the ports left for your own services either way.
A POD_ID that matches nothing exits 5, so a typo cannot read as an empty pod.
With --json the command never blocks on the interactive setup prompt: a missing
API key surfaces as the JSON error envelope instead.