Journald Writes log messages to journald.The journald daemon must be running on the host machine. Syslog Writes logging messages to the syslog facility.The syslog daemon must be running on the host machine. Json-file The logs are formatted as JSON.The default logging driver for Docker. Local Logs are stored in a custom format designed for minimal overhead. None No logs are available for the container and docker logs does not return any output. The various log mechanisms are listed in the Log in the Plugins item in the result of the docker info command above. There is a corresponding introduction on the docker official website:
#DOCKER SYSLOG DRIVER UPDATE#
#Static view log-do not update docker logs container ID #DynamicĪlthough we can view the logs, where are these logs stored? Here we need to mention the concept of Docker logging driver. Docker logging driver is a mechanism for Docker to collect container logs and internal running service logs.These mechanisms are collectively referred to as logging drivers. You can view it through the docker info command (maybe some can't, it may only list the log mechanisms currently supported by docker). Plugins: Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog After docker starts the container, the default Docker log will be sent to the container's standard output device (STDOUT) and standard error device (STDERR), where STDOUT and STDERR are actually the container's console terminal. You can use the docker logs command to view the logs output by a certain container, as follows: