Everything a containerized application writes to stdout and stderr is handled and redirected somewhere by a container engine. For example, the Docker container engine redirects those two streams to a logging driver

The docker logs command is not available for drivers other than json-file and journald.

logging driver

To configure the Docker daemon to default to a specific logging driver, set the value of log-driver to the name of the logging driver in the daemon.json file

The default logging driver is json-file. Thus, the default output for commands such as docker inspect is JSON

  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3",
    "labels": "bigo.logg",
    "env": "os"
  • check the current driver

    docker info --format '{{.LoggingDriver}}'


the default location


or check log location via

docker inspect --format='{{.LogPath}}' $INSTANCE_ID

Supported logging drivers

Driver Description
none No logs are available for the container and docker logs does not return any output.
json-file The logs are formatted as JSON. The default logging driver for Docker.
local Writes logs messages to local filesystem in binary files using Protobuf.
syslog Writes logging messages to the syslog facility. The syslog daemon must be running on the host machine.
journald Writes log messages to journald. The journald daemon must be running on the host machine.
gelf Writes log messages to a Graylog Extended Log Format (GELF) endpoint such as Graylog or Logstash.
fluentd Writes log messages to fluentd (forward input). The fluentd daemon must be running on the host machine.
awslogs Writes log messages to Amazon CloudWatch Logs.


  • 方法1

    docker run -it --rm --entrypoint /bin/sh curl:v1
  • 方法2 通过Dockerfile从镜像再建一个镜像,并重定义ENTRYPOINT

view real time logging of Docker containers

docker logs -f