1podman-container-logs(1)    General Commands Manual   podman-container-logs(1)
2
3
4

NAME

6       podman-container-logs (podman-logs) - Fetch the logs of one or more
7       containers
8
9

SYNOPSIS

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

DESCRIPTION

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

OPTIONS

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

EXAMPLE

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

SEE ALSO

126       podman(1), podman-run(1), podman-container-rm(1)
127
128

HISTORY

130       February 2018, Updated by Brent Baude ⟨bbaude@redhat.com⟩
131
132
133       August 2017, Originally compiled by Ryan Cole ⟨rycole@redhat.com⟩
134
135
136
137                                                      podman-container-logs(1)
Impressum