podman-pod-top(1)
π podman-pod-top(1) β General Commands Manual, bestie edition π
okay so you found the podman-pod-top page in the General Commands Manual and honestly? it's giving "who is running what inside my pod" and I'm obsessed. let's get into it π«Ά
β¨ NAME β¨
podman-pod-top β Display the running processes of containers in a pod
like literally it shows you the processes chugging along inside the containers of a pod. main character surveillance energy π
πΈ SYNOPSIS πΈ
podman pod top [options] pod [format-descriptors]
π DESCRIPTION π
Display the running processes of containers in a pod. that's the whole vibe π
now, the format-descriptors? they're ps(1)-compatible AIX format descriptors, but lowkey extended so they can also print extra info β like the seccomp mode or the effective capabilities of a given process. fancy fr fr β¨
and here's the cute part: you can pass those descriptors either as separate arguments or as a single comma-separated argument. dealer's choice, bestie π
β¨ OPTIONS β¨
--help,-hβ Print usage statement. the classic "help me pls" move π--latest,-lβ Instead of providing the pod name or ID, use the last created pod. note that the last started pod can be from other users of Podman on the host machine π (and heads up: this option is not available with the remote Podman client, including Mac and Windows machines β excluding WSL2 π)
π¦ FORMAT DESCRIPTORS π¦
For a full list of available descriptors, see podman-top(1). yeah go read that one, it's the source of truth π
π EXAMPLES π
Print top data for the specified pod π
By default, podman-pod-top prints data similar to ps -ef:
$ podman pod top b031293491cc
USER PID PPID %CPU ELAPSED TTY TIME COMMAND
root 1 0 0.000 2h5m38.737137571s ? 0s top
root 8 0 0.000 2h5m15.737228361s ? 0s top
and the output can be controlled by specifying format descriptors as arguments after the pod. you're the director of this movie, bestie π¬
Print specific fields on the latest pod π«
Print the pod top data fields pid, seccomp, args and %C on the latest pod created. (This -l option is not available with the remote Podman client, including Mac and Windows machines β excluding WSL2)
$ podman pod top -l pid seccomp args %C
PID SECCOMP COMMAND %CPU
1 filter top 0.000
1 filter /bin/sh 0.000
ate. no crumbs. π₯
π SEE ALSO π
podman(1), podman-pod(1), ps(1), seccomp(2), proc(5), capabilities(7)
go read those too, they're the friend group π«Ά
π HISTORY π
August 2018, Originally compiled by Peter Hunt pehunt@redhat.com β¨mailto:pehunt@redhat.comβ© β thank you Peter, iconic behavior π
and that's the whole page, bestie!! this was podman-pod-top(1) from the General Commands Manual, footer says podman-pod-top(1) β so like, go peek at your pods' processes and slay π
β¨π
π¦ where this page comes from
- arch rolling: podman-docker 6.1.4-1 Β· Apache-2.0
- fedora 43: podman-docker 5:5.6.2-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 43: podman-docker 5:5.8.4-1.fc43
- fedora 43: podman-docker 5:5.8.8-1.fc43
- fedora 43: podman-docker 5:5.8.9-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.7-1.fc44
- fedora 44: podman-docker 5:5.8.9-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- ubuntu resolute: podman-docker 5.7.0+ds2-3build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms