podman-pod-top(1)

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

πŸ’… 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 🌈

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 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