1podman-logs(1)()                                              podman-logs(1)()
2
3
4

NAME

6       podman-logs - Display the logs of one or more containers
7
8

SYNOPSIS

10       podman logs [options] container [container...]
11
12
13       podman container logs [options] container [container...]
14
15

DESCRIPTION

17       The  podman  logs command batch-retrieves whatever logs are present for
18       one or more containers at the time of execution.  This does not guaran‐
19       tee  execution  order  when combined with podman run (i.e. your run may
20       not have generated any logs at the time you execute podman logs).
21
22

OPTIONS

24   --color
25       Output the containers with different colors in the log.
26
27
28   --follow, -f
29       Follow log output.  Default is false.
30
31
32       Note: If you are following a container which  is  removed  podman  con‐
33       tainer  rm  or  removed  on  exit  podman run --rm ..., then there is a
34       chance that the log file will be removed before podman logs  reads  the
35       final content.
36
37
38   --latest, -l
39       Instead  of  providing  the  container name or ID, use the last created
40       container. If you use methods other than Podman to run containers  such
41       as  CRI-O,  the  last  started  container could be from either of those
42       methods. (This option is not available with the remote  Podman  client,
43       including Mac and Windows (excluding WSL2) machines)
44
45
46   --names, -n
47       Output the container name in the log
48
49
50   --since=TIMESTAMP
51       Show  logs  since TIMESTAMP. The --since option can be Unix timestamps,
52       date formatted timestamps, or Go duration  strings  (e.g.  10m,  1h30m)
53       computed  relative  to the client machine's time. Supported formats for
54       date   formatted   time   stamps    include    RFC3339Nano,    RFC3339,
55       2006-01-02T15:04:05,  2006-01-02T15:04:05.999999999,  2006-01-02Z07:00,
56       and 2006-01-02.
57
58
59   --tail=LINES
60       Output the specified number of LINES at the end  of  the  logs.   LINES
61       must be an integer.  Defaults to -1, which prints all lines
62
63
64   --timestamps, -t
65       Show timestamps in the log outputs.  The default is false
66
67
68   --until=TIMESTAMP
69       Show  logs  until TIMESTAMP. The --until option can be Unix timestamps,
70       date formatted timestamps, or Go duration  strings  (e.g.  10m,  1h30m)
71       computed  relative  to the client machine's time. Supported formats for
72       date   formatted   time   stamps    include    RFC3339Nano,    RFC3339,
73       2006-01-02T15:04:05,  2006-01-02T15:04:05.999999999,  2006-01-02Z07:00,
74       and 2006-01-02.
75
76

EXAMPLE

78       To view a container's logs:
79
80
81              podman logs -t b3f2436bdb978c1d33b1387afb5d7ba7e3243ed2ce908db431ac0069da86cb45
82
83              2017/08/07 10:16:21 Seeked /var/log/crio/pods/eb296bd56fab164d4d3cc46e5776b54414af3bf543d138746b25832c816b933b/c49f49788da14f776b7aa93fb97a2a71f9912f4e5a3e30397fca7dfe0ee0367b.log - &{Offset:0 Whence:0}
84              1:C 07 Aug 14:10:09.055 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
85              1:C 07 Aug 14:10:09.055 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
86              1:C 07 Aug 14:10:09.055 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
87              1:M 07 Aug 14:10:09.055 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
88              1:M 07 Aug 14:10:09.055 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
89              1:M 07 Aug 14:10:09.055 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
90              1:M 07 Aug 14:10:09.056 * Running mode=standalone, port=6379.
91              1:M 07 Aug 14:10:09.056 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
92              1:M 07 Aug 14:10:09.056 # Server initialized
93
94
95
96       To view only the last two lines in container's log:
97
98
99              podman logs --tail 2 b3f2436bdb97
100
101              # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
102              # Server initialized
103
104
105
106       To view all containers logs:
107
108
109              podman logs -t --since 0 myserver
110
111              1:M 07 Aug 14:10:09.055 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
112              1:M 07 Aug 14:10:09.055 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
113              1:M 07 Aug 14:10:09.056 * Running mode=standalone, port=6379.
114              1:M 07 Aug 14:10:09.056 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
115              1:M 07 Aug 14:10:09.056 # Server initialized
116
117
118
119       To view a containers logs since a certain time:
120
121
122              podman logs -t --since 2017-08-07T10:10:09.055837383-04:00 myserver
123
124              1:M 07 Aug 14:10:09.055 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
125              1:M 07 Aug 14:10:09.055 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
126              1:M 07 Aug 14:10:09.056 * Running mode=standalone, port=6379.
127              1:M 07 Aug 14:10:09.056 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
128              1:M 07 Aug 14:10:09.056 # Server initialized
129
130
131
132       To view a container's logs generated in the last 10 minutes:
133
134
135              podman logs --since 10m myserver
136
137              # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
138              # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
139
140
141
142       To view a container's logs until 30 minutes ago:
143
144
145              podman logs --until 30m myserver
146
147              AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 10.0.2.100. Set the 'ServerName' directive globally to suppress this message
148              AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 10.0.2.100. Set the 'ServerName' directive globally to suppress this message
149              [Tue Jul 20 13:18:14.223727 2021] [mpm_event:notice] [pid 1:tid 140021067187328] AH00489: Apache/2.4.48 (Unix) configured -- resuming normal operations
150              [Tue Jul 20 13:18:14.223819 2021] [core:notice] [pid 1:tid 140021067187328] AH00094: Command line: 'httpd -D FOREGROUND'
151
152
153

SEE ALSO

155       podman(1), podman-run(1), podman-container-rm(1)
156
157

HISTORY

159       February   2018,   Updated    by    Brent    Baude    bbaude@redhat.com
160       ⟨mailto:bbaude@redhat.com⟩
161
162
163       August   2017,  Originally  compiled  by  Ryan  Cole  rycole@redhat.com
164       ⟨mailto:rycole@redhat.com⟩
165
166
167
168                                                              podman-logs(1)()
Impressum