docker logsEstimated reading time: 2 minutes
Fetch the logs of a container
docker logs [OPTIONS] CONTAINER
||Show extra details provided to logs|
||Follow log output|
||Show logs since timestamp (e.g. 2013-01-02T13:23:37) or relative (e.g. 42m for 42 minutes)|
||Number of lines to show from the end of the logs|
|docker||The base command for the Docker CLI.|
docker logs command batch-retrieves logs present at the time of execution.
Note: this command is only functional for containers that are started with the
For more information about selecting and configuring logging drivers, refer to Configure logging drivers.
docker logs --follow command will continue streaming the new output from
Passing a negative number or a non-integer to
--tail is invalid and the
value is set to
all in that case.
docker logs --timestamps command will add an RFC3339Nano timestamp
, for example
2014-09-16T06:17:46.000000000Z, to each
log entry. To ensure that the timestamps are aligned the
nano-second part of the timestamp will be padded with zero when necessary.
docker logs --details command will add on extra attributes, such as
environment variables and labels, provided to
--log-opt when creating the
--since option shows only the container logs generated after
a given date. You can specify the date as an RFC 3339 date, a UNIX
timestamp, or a Go duration string (e.g.
3h). Besides RFC3339 date
format you may also use RFC3339Nano,
2006-01-02. The local
timezone on the client will be used if you do not provide either a
Z or a
+-00:00 timezone offset at the end of the timestamp. When providing Unix
timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap
seconds (aka Unix epoch or Unix time), and the optional .nanoseconds field is a
fraction of a second no more than nine digits long. You can combine the
--since option with either or both of the