podman-container-top(1)

1podman-top(1)               General Commands Manual              podman-top(1)
2
3
4

NAME

6       podman-top - Display the running processes of a container
7
8

SYNOPSIS

10       podman top [options] container [format-descriptors]
11
12
13       podman container top [options] container [format-descriptors]
14
15

DESCRIPTION

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

OPTIONS

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       including Mac and Windows (excluding WSL2) machines)
40
41

FORMAT DESCRIPTORS

43       The following descriptors are supported in addition to the  AIX  format
44       descriptors mentioned in ps (1):
45
46
47       args, capbnd, capeff, capinh, capprm, comm, etime, group, hgroup, hpid,
48       huser, label, nice, pcpu, pgid,  pid,  ppid,  rgroup,  ruser,  seccomp,
49       state, time, tty, user, vsz
50
51
52       capbnd
53
54
55       Set  of  bounding  capabilities. See capabilities (7) for more informa‐
56       tion.
57
58
59       capeff
60
61
62       Set of effective capabilities. See capabilities (7) for  more  informa‐
63       tion.
64
65
66       capinh
67
68
69       Set of inheritable capabilities. See capabilities (7) for more informa‐
70       tion.
71
72
73       capprm
74
75
76       Set of permitted capabilities. See capabilities (7) for  more  informa‐
77       tion.
78
79
80       hgroup
81
82
83       The corresponding effective group of a container process on the host.
84
85
86       hpid
87
88
89       The corresponding host PID of a container process.
90
91
92       huser
93
94
95       The corresponding effective user of a container process on the host.
96
97
98       label
99
100
101       Current security attributes of the process.
102
103
104       seccomp
105
106
107       Seccomp  mode  of  the  process (i.e., disabled, strict or filter). See
108       seccomp (2) for more information.
109
110
111       state
112
113
114       Process state codes (e.g, R for running, S for sleeping).  See  proc(5)
115       for more information.
116
117
118       stime
119
120
121       Process start time (e.g, "2019-12-09 10:50:36 +0100 CET).
122
123

EXAMPLES

125       By default, podman-top prints data similar to ps -ef:
126
127
128              $ podman top f5a62a71b07
129              USER   PID   PPID   %CPU    ELAPSED         TTY     TIME   COMMAND
130              root   1     0      0.000   20.386825206s   pts/0   0s     sh
131              root   7     1      0.000   16.386882887s   pts/0   0s     sleep
132              root   8     1      0.000   11.386886562s   pts/0   0s     vi
133
134
135
136       The  output can be controlled by specifying format descriptors as argu‐
137       ments after the container:
138
139
140              $ podman top -l pid seccomp args %C
141              PID   SECCOMP   COMMAND     %CPU
142              1     filter    sh          0.000
143              8     filter    vi /etc/    0.000
144
145
146
147       Podman will fallback to executing ps(1) in the container if an  unknown
148       descriptor is specified.
149
150
151              $ podman top -l -- aux
152              USER   PID   PPID   %CPU    ELAPSED             TTY   TIME   COMMAND
153              root   1     0      0.000   1h2m12.497061672s   ?     0s     sleep 100000
154
155
156

HISTORY

162       July  2018,  Introduce  format  descriptors by Valentin Rothberg vroth‐
163       berg@suse.com ⟨mailto:vrothberg@suse.com⟩
164
165
166       December 2017, Originally compiled  by  Brent  Baude  bbaude@redhat.com
167       ⟨mailto:bbaude@redhat.com⟩
168
169
170
171                                                                 podman-top(1)