podman-pod-inspect(1)

πŸ“¦
version 6.1.4 Β· 6 versions
, in arch rolling, fedora 43, fedora 44, ubuntu resolute

okay so bestie, welcome to the podman-pod-inspect(1) manual page πŸ’…βœ¨ this one's all about peeking at your pods and getting the full tea. no cap, it's lowkey iconic.


✨ NAME ✨

podman-pod-inspect β€” Display information describing a pod

πŸ¦‹ SYNOPSIS πŸ¦‹

podman pod inspect [options] pod ...

πŸ’– DESCRIPTION πŸ’–

So this command shows you all the config and state deets for a given pod β€” and it also spills the tea on the containers that belong to that pod. πŸ’…

πŸ‘‘ OPTIONS πŸ‘‘

🌸 --format, -f=format 🌸

Change the default output format. This can be a supported type like json or a Go template. Valid placeholders for the Go template are listed below:

  • .BlkioDeviceReadBps β€” Block I/O Device Read, in bytes/sec
  • .BlkioDeviceWriteBps β€” Block I/O Device Read, in bytes/sec
  • .BlkioWeight β€” Block I/O Weight
  • .BlkioWeightDevice β€” Block I/O Device Weight
  • .CgroupParent β€” Pod cgroup parent
  • .CgroupPath β€” Pod cgroup path
  • .Containers β€” Pod containers
  • .CPUPeriod β€” CPU period
  • .CPUQuota β€” CPU quota
  • .CPUSetCPUs β€” CPU Set CPUs
  • .CPUSetMems β€” CPU Set Mems
  • .CPUShares β€” CPU Shares
  • .CreateCgroup β€” Whether cgroup was created
  • .CreateCommand β€” Create command
  • .Created ... β€” Time when the pod was created
  • .CreateInfra β€” Whether infrastructure created
  • .Devices β€” Devices
  • .ExitPolicy β€” Exit policy
  • .Hostname β€” Pod hostname
  • .ID β€” Pod ID
  • .InfraConfig ... β€” Infra config (contains further fields)
  • .InfraContainerID β€” Pod infrastructure ID
  • .InspectPodData ... β€” Nested structure, for experts only
  • .Labels ... β€” Pod labels
  • .LockNumber β€” Number of the pod's Libpod lock
  • .MemoryLimit β€” Memory limit, bytes
  • .MemorySwap β€” Memory swap limit, in bytes
  • .Mounts β€” Mounts
  • .Name β€” Pod name
  • .Namespace β€” Namespace
  • .NumContainers β€” Number of containers in the pod
  • .RestartPolicy β€” Restart policy of the pod
  • .SecurityOpts β€” Security options
  • .SharedNamespaces β€” Pod shared namespaces
  • .State β€” Pod state
  • .VolumesFrom β€” Volumes from

πŸŽ€ --latest, -l πŸŽ€

Instead of providing the pod name or ID, use the last created pod.

Note: the last started pod can be from other users of Podman on the host machine.
Heads up: This option is <strong>not</strong> available with the remote Podman client, including Mac and Windows (excluding WSL2) machines.

✨ EXAMPLE ✨

Okay bestie, time for the fun part β€” let's actually see this thing in action πŸ’…


Peep a specific pod:

$ podman pod inspect foobar
[
     {
         "Id": "3513ca70583dd7ef2bac83331350f6b6c47d7b4e526c908e49d89ebf720e4693",
         "Name": "foobar",
         "Labels": {},
         "CgroupParent": "/libpod_parent",
         "CreateCgroup": true,
         "Created": "2018-08-08T11:15:18.823115347-05:00"
         "State": "created",
         "Hostname": "",
         "SharedNamespaces": [
              "uts",
              "ipc",
              "net"
         ]
         "CreateInfra": false,
         "InfraContainerID": "1020dd70583dd7ff2bac83331350f6b6e007de0d026c908e49d89ebf891d4699"
         "CgroupPath": ""
         "Containers": [
              {
                   "id": "d53f8bf1e9730281264aac6e6586e327429f62c704abea4b6afb5d8a2b2c9f2c",
                   "state": "configured"
              }
         ]
     }
]

Look at all that JSON, it's giving full transparency ✨


Just want the name and the state? Say less:

$ podman pod inspect --format "{{.Name}}\t{{.State}}" mypod
mypod     Running

That little \t is a tab btw, so it lines up all pretty πŸŽ€


Pod ID plus how many containers it's holding:

$ podman pod inspect mypod --format "Pod {{.Name}} ({{.ID}}) has {{.NumContainers}} containers"
Pod mypod (605f5f776e101a6e0ad11ea802cae25eabf299da77122f2963fa65dc6ccf6717) has 2 containers

{{.NumContainers}} is so handy, no cap 🫢


Creation time + which namespaces are being shared:

$ podman pod inspect mypod --format "Created: {{.Created}}\nShared: {{.SharedNamespaces}}"
Created: 2025-08-14 21:16:05.861363099 +0000 UTC
Shared: [net uts ipc]

\n for the newline, {{.SharedNamespaces}} for the tea β˜•


Resource limits, come get your numbers:

$ podman pod inspect --format "Memory: {{.MemoryLimit}}, CPU Period: {{.CPUPeriod}}, CPU Quota: {{.CPUQuota}}" mypod
Memory: 1073741824, CPU Period: 100000, CPU Quota: 50000

And if you wanna see every container inside the pod β€” range girlies rise up:

$ podman pod inspect --format "{{range .Containers}}{{.Id}}: {{.State}} {{end}}" mypod
e907f7902decca9d6b600b4d3cca9541d9b89dd726b2af7ad2eba05d2a97083f: running c5a53050a31aed71c55cb6a31b9564c69a1009f77750f3f0e8093bd98fcd8918: running
πŸ’€ note that those two containers just get squished together on one line β€” if you want them separated, add a \n in there yourself, bestie. The manpage shows it raw, so raw it stays.

🌸 SEE ALSO 🌸


πŸ’œ HISTORY πŸ’œ

August 2018, originally compiled by Brent Baude bbaude@redhat.com ⟨mailto:bbaude@redhat.com⟩

Like, the original original. Respect the elders πŸ«‘πŸ‘‘


okay that's the whole page bestie, you made it to the end πŸŽ‰ this was podman-pod-inspect(1), and the lore goes all the way back to August 2018 β€” iconic behavior from a page that's been serving format-string realness for years. now go inspect something, you've got this πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from