github.com/brahmaroutu/docker@v1.2.1-0.20160809185609-eb28dde01f16/docs/reference/commandline/logs.md (about)

     1  <!--[metadata]>
     2  +++
     3  title = "logs"
     4  description = "The logs command description and usage"
     5  keywords = ["logs, retrieve, docker"]
     6  [menu.main]
     7  parent = "smn_cli"
     8  +++
     9  <![end-metadata]-->
    10  
    11  # logs
    12  
    13  ```markdown
    14  Usage:  docker logs [OPTIONS] CONTAINER
    15  
    16  Fetch the logs of a container
    17  
    18  Options:
    19        --details        Show extra details provided to logs
    20    -f, --follow         Follow log output
    21        --help           Print usage
    22        --since string   Show logs since timestamp
    23        --tail string    Number of lines to show from the end of the logs (default "all")
    24    -t, --timestamps     Show timestamps
    25  ```
    26  
    27  > **Note**: this command is available only for containers with `json-file` and
    28  > `journald` logging drivers.
    29  
    30  The `docker logs` command batch-retrieves logs present at the time of execution.
    31  
    32  The `docker logs --follow` command will continue streaming the new output from
    33  the container's `STDOUT` and `STDERR`.
    34  
    35  Passing a negative number or a non-integer to `--tail` is invalid and the
    36  value is set to `all` in that case.
    37  
    38  The `docker logs --timestamps` command will add an [RFC3339Nano timestamp](https://golang.org/pkg/time/#pkg-constants)
    39  , for example `2014-09-16T06:17:46.000000000Z`, to each
    40  log entry. To ensure that the timestamps are aligned the
    41  nano-second part of the timestamp will be padded with zero when necessary.
    42  
    43  The `docker logs --details` command will add on extra attributes, such as
    44  environment variables and labels, provided to `--log-opt` when creating the
    45  container.
    46  
    47  The `--since` option shows only the container logs generated after
    48  a given date. You can specify the date as an RFC 3339 date, a UNIX
    49  timestamp, or a Go duration string (e.g. `1m30s`, `3h`). Besides RFC3339 date
    50  format you may also use RFC3339Nano, `2006-01-02T15:04:05`,
    51  `2006-01-02T15:04:05.999999999`, `2006-01-02Z07:00`, and `2006-01-02`. The local
    52  timezone on the client will be used if you do not provide either a `Z` or a
    53  `+-00:00` timezone offset at the end of the timestamp. When providing Unix
    54  timestamps enter seconds[.nanoseconds], where seconds is the number of seconds
    55  that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap
    56  seconds (aka Unix epoch or Unix time), and the optional .nanoseconds field is a
    57  fraction of a second no more than nine digits long. You can combine the
    58  `--since` option with either or both of the `--follow` or `--tail` options.