1podman-top(1)() podman-top(1)()
2
3
4
6 podman-top - Display the running processes of a container
7
8
10 podman top [options] container [format-descriptors]
11
12
13 podman container top [options] container [format-descriptors]
14
15
17 Display the running processes of the container. The format-descriptors
18 are ps (1) compatible AIX format descriptors but extended to print ad‐
19 ditional information, such as the seccomp mode or the effective capa‐
20 bilities of a given process. The descriptors can either be passed as
21 separated arguments or as a single comma-separated argument. Note that
22 you can also specify options and or flags of ps(1); in this case, Pod‐
23 man will fallback to executing ps with the specified arguments and
24 flags in the container. Please use the "h*" descriptors if you want to
25 extract host-related information. For instance, podman top $name hpid
26 huser to display the PID and user of the processes in the host context.
27
28
30 --help, -h
31 Print usage statement
32
33
34 --latest, -l
35 Instead of providing the container name or ID, use the last created
36 container. If you use methods other than Podman to run containers such
37 as CRI-O, the last started container could be from either of those
38 methods.(This option is not available with the remote Podman client)
39
40
42 The following descriptors are supported in addition to the AIX format
43 descriptors mentioned in ps (1):
44
45
46 args, capbnd, capeff, capinh, capprm, comm, etime, group, hgroup, hpid,
47 huser, label, nice, pcpu, pgid, pid, ppid, rgroup, ruser, seccomp,
48 state, time, tty, user, vsz
49
50
51 capbnd
52
53
54 Set of bounding capabilities. See capabilities (7) for more informa‐
55 tion.
56
57
58 capeff
59
60
61 Set of effective capabilities. See capabilities (7) for more informa‐
62 tion.
63
64
65 capinh
66
67
68 Set of inheritable capabilities. See capabilities (7) for more informa‐
69 tion.
70
71
72 capprm
73
74
75 Set of permitted capabilities. See capabilities (7) for more informa‐
76 tion.
77
78
79 hgroup
80
81
82 The corresponding effective group of a container process on the host.
83
84
85 hpid
86
87
88 The corresponding host PID of a container process.
89
90
91 huser
92
93
94 The corresponding effective user of a container process on the host.
95
96
97 label
98
99
100 Current security attributes of the process.
101
102
103 seccomp
104
105
106 Seccomp mode of the process (i.e., disabled, strict or filter). See
107 seccomp (2) for more information.
108
109
110 state
111
112
113 Process state codes (e.g, R for running, S for sleeping). See proc(5)
114 for more information.
115
116
117 stime
118
119
120 Process start time (e.g, "2019-12-09 10:50:36 +0100 CET).
121
122
124 By default, podman-top prints data similar to ps -ef:
125
126
127 $ podman top f5a62a71b07
128 USER PID PPID %CPU ELAPSED TTY TIME COMMAND
129 root 1 0 0.000 20.386825206s pts/0 0s sh
130 root 7 1 0.000 16.386882887s pts/0 0s sleep
131 root 8 1 0.000 11.386886562s pts/0 0s vi
132
133
134
135 The output can be controlled by specifying format descriptors as argu‐
136 ments after the container:
137
138
139 $ podman top -l pid seccomp args %C
140 PID SECCOMP COMMAND %CPU
141 1 filter sh 0.000
142 8 filter vi /etc/ 0.000
143
144
145
146 Podman will fallback to executing ps(1) in the container if an unknown
147 descriptor is specified.
148
149
150 $ podman top -l -- aux
151 USER PID PPID %CPU ELAPSED TTY TIME COMMAND
152 root 1 0 0.000 1h2m12.497061672s ? 0s sleep 100000
153
154
155
157 podman(1), ps(1), seccomp(2), proc(5), capabilities(7)
158
159
161 July 2018, Introduce format descriptors by Valentin Rothberg vroth‐
162 berg@suse.com ⟨mailto:vrothberg@suse.com⟩
163
164
165 December 2017, Originally compiled by Brent Baude bbaude@redhat.com
166 ⟨mailto:bbaude@redhat.com⟩
167
168
169
170 podman-top(1)()