github.com/crquan/docker@v1.8.1/man/docker-logs.1.md (about) 1 % DOCKER(1) Docker User Manuals 2 % Docker Community 3 % JUNE 2014 4 # NAME 5 docker-logs - Fetch the logs of a container 6 7 # SYNOPSIS 8 **docker logs** 9 [**-f**|**--follow**[=*false*]] 10 [**--help**] 11 [**--since**[=*SINCE*]] 12 [**-t**|**--timestamps**[=*false*]] 13 [**--tail**[=*"all"*]] 14 CONTAINER 15 16 # DESCRIPTION 17 The **docker logs** command batch-retrieves whatever logs are present for 18 a container at the time of execution. This does not guarantee execution 19 order when combined with a docker run (i.e., your run may not have generated 20 any logs at the time you execute docker logs). 21 22 The **docker logs --follow** command combines commands **docker logs** and 23 **docker attach**. It will first return all logs from the beginning and 24 then continue streaming new output from the container’s stdout and stderr. 25 26 **Warning**: This command works only for **json-file** logging driver. 27 28 # OPTIONS 29 **--help** 30 Print usage statement 31 32 **-f**, **--follow**=*true*|*false* 33 Follow log output. The default is *false*. 34 35 **--since**="" 36 Show logs since timestamp 37 38 **-t**, **--timestamps**=*true*|*false* 39 Show timestamps. The default is *false*. 40 41 **--tail**="all" 42 Output the specified number of lines at the end of logs (defaults to all logs) 43 44 The `--since` option shows only the container logs generated after 45 a given date. You can specify the date as an RFC 3339 date, a UNIX 46 timestamp, or a Go duration string (e.g. `1m30s`, `3h`). Docker computes 47 the date relative to the client machine’s time. You can combine 48 the `--since` option with either or both of the `--follow` or `--tail` options. 49 50 # HISTORY 51 April 2014, Originally compiled by William Henry (whenry at redhat dot com) 52 based on docker.com source material and internal work. 53 June 2014, updated by Sven Dowideit <SvenDowideit@home.org.au> 54 July 2014, updated by Sven Dowideit <SvenDowideit@home.org.au> 55 April 2015, updated by Ahmet Alp Balkan <ahmetalpbalkan@gmail.com>