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   --follow, -f
25       Follow log output.  Default is false.
26
27
28       Note: If you are following a container which  is  removed  podman  con‐
29       tainer  rm  or  removed  on  exit  podman run --rm ..., then there is a
30       chance the the log file will be removed before podman  logs  reads  the
31       final content.
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.
39
40
41       The latest option is not supported on the remote client.
42
43
44   --names, -n
45       Output the container name in the log
46
47
48   --since=TIMESTAMP
49       Show logs since TIMESTAMP. The --since option can be  Unix  timestamps,
50       date  formatted  timestamps,  or  Go duration strings (e.g. 10m, 1h30m)
51       computed relative to the client machine's time. Supported  formats  for
52       date    formatted    time    stamps   include   RFC3339Nano,   RFC3339,
53       2006-01-02T15:04:05,  2006-01-02T15:04:05.999999999,  2006-01-02Z07:00,
54       and 2006-01-02.
55
56
57   --tail=LINES
58       Output  the  specified  number  of LINES at the end of the logs.  LINES
59       must be an integer.  Defaults to -1, which prints all lines
60
61
62   --timestamps, -t
63       Show timestamps in the log outputs.  The default is false
64
65

EXAMPLE

67       To view a container's logs:
68
69
70              podman logs -t b3f2436bdb978c1d33b1387afb5d7ba7e3243ed2ce908db431ac0069da86cb45
71
72              2017/08/07 10:16:21 Seeked /var/log/crio/pods/eb296bd56fab164d4d3cc46e5776b54414af3bf543d138746b25832c816b933b/c49f49788da14f776b7aa93fb97a2a71f9912f4e5a3e30397fca7dfe0ee0367b.log - {Offset:0 Whence:0}
73              1:C 07 Aug 14:10:09.055 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
74              1:C 07 Aug 14:10:09.055 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
75              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
76              1:M 07 Aug 14:10:09.055 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
77              1:M 07 Aug 14:10:09.055 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
78              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'.
79              1:M 07 Aug 14:10:09.056 * Running mode=standalone, port=6379.
80              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.
81              1:M 07 Aug 14:10:09.056 # Server initialized
82
83
84
85       To view only the last two lines in container's log:
86
87
88              podman logs --tail 2 b3f2436bdb97
89
90              # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
91              # Server initialized
92
93
94
95       To view a containers logs since a certain time:
96
97
98              podman logs -t --since 2017-08-07T10:10:09.055837383-04:00 myserver
99
100              1:M 07 Aug 14:10:09.055 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
101              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'.
102              1:M 07 Aug 14:10:09.056 * Running mode=standalone, port=6379.
103              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.
104              1:M 07 Aug 14:10:09.056 # Server initialized
105
106
107
108       To view a container's logs generated in the last 10 minutes:
109
110
111              podman logs --since 10m myserver
112
113              # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
114              # 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'.
115
116
117

SEE ALSO

119       podman(1), podman-run(1), podman-container-rm(1)
120
121

HISTORY

123       February   2018,   Updated    by    Brent    Baude    bbaude@redhat.com
124       ⟨mailto:bbaude@redhat.com⟩
125
126
127       August   2017,  Originally  compiled  by  Ryan  Cole  rycole@redhat.com
128       ⟨mailto:rycole@redhat.com⟩
129
130
131
132                                                              podman-logs(1)()
Impressum