From b04bb8be45e4dd5c24c5321b2498803f2470aade Mon Sep 17 00:00:00 2001 From: Emiliano 'AlberT' Gabrielli Date: Tue, 12 Jun 2018 16:28:45 +0200 Subject: [PATCH] fix nginx logs links the log file is linked to the device, not viceversa :) --- config/containers/logging/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/config/containers/logging/index.md b/config/containers/logging/index.md index 95d699e0c5..4a5440daa8 100644 --- a/config/containers/logging/index.md +++ b/config/containers/logging/index.md @@ -37,9 +37,9 @@ In the first case, your logs are processed in other ways and you may choose not to use `docker logs`. In the second case, the official `nginx` image shows one workaround, and the official Apache `httpd` image shows another. -The official `nginx` image creates a symbolic link from -`/dev/stdout` to `/var/log/nginx/access.log`, and creates another symbolic link -from `/dev/stderr` to `/var/log/nginx/error.log`, overwriting the log files and +The official `nginx` image creates a symbolic link from `/var/log/nginx/access.log` +to `/dev/stdout`, and creates another symbolic link +from `/var/log/nginx/error.log` to `/dev/stderr`, overwriting the log files and causing logs to be sent to the relevant special device instead. See the [Dockerfile](https://github.com/nginxinc/docker-nginx/blob/8921999083def7ba43a06fabd5f80e4406651353/mainline/jessie/Dockerfile#L21-L23).