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