Runtime error after first run about dockerize HOT 9 CLOSED

Do I need some kind of go standard library?

from dockerize.

Could this be causing trouble?

/var/log/nginx# ls -al
total 8
drwxr-xr-x 2 root root 4096 Oct 28 22:01 .
drwxr-xr-x 9 root root 4096 Nov 10 15:06 ..
lrwxrwxrwx 1 root root   11 Oct 28 22:01 access.log -> /dev/stdout
lrwxrwxrwx 1 root root   11 Oct 28 22:01 error.log -> /dev/stderr

from dockerize.

If I leave off -stdout /var/log/nginx/access.log -stderr /var/log/nginx/error.log it runs (though I'm not sure yet if it works)

from dockerize.

Oh! the offical docker nginx repo makes these links:

https://github.com/nginxinc/docker-nginx/blob/4e5332fa50a1f8f73657417c6bfe249bbb3b110d/Dockerfile#L15

RUN ln -sf /dev/stdout /var/log/nginx/access.log
RUN ln -sf /dev/stderr /var/log/nginx/error.log

Is that what's causing the failure?

from dockerize.

Can confirm that replacing the links with regular files fixes the stacktrace, when using -stdout /var/log/nginx/access.log -stderr /var/log/nginx/error.log

from dockerize.

Proposed fix:

Defensively code the part that redirects log files to stdout/error.

from dockerize.

I'd do it, but I'm no go pro!

from dockerize.

Could this be related to overlayfs?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882147
moby/moby#11705

from dockerize.

RUN ln -sf /dev/stdout /var/log/nginx/access.log
RUN ln -sf /dev/stderr /var/log/nginx/error.log

It's have same effect like dockerize's -stdout /var/log/nginx/access.log -stderr /var/log/nginx/error.log, but the ln -sf way is better, because dockerzie don't cleans already forwarded lines from logs and container continues growing.

from dockerize.