Dockerfile: [Severe bug] All nginx derived containers are breaking
Which ever nginx derived image I try to run, I see a bunch of config errors. For example:
docker run -p 80:80 -it webdevops/hhvm-nginx
is throwing out the following error log.
Digest: sha256:acc8e9c6557b63c61485eeebae8989ec58ef69ed4ff4b1dd85f7bb3abeaeca1d
Status: Downloaded newer image for webdevops/hhvm-nginx:latest
-> Executing /opt/docker/provision/entrypoint.d/05-permissions.sh
-> Executing /opt/docker/bin/service.d/supervisor.d//10-init.sh
2017-05-20 01:17:46,588 CRIT Set uid to user 0
2017-05-20 01:17:46,589 WARN Included extra file "/opt/docker/etc/supervisor.d/cron.conf" during parsing
2017-05-20 01:17:46,589 WARN Included extra file "/opt/docker/etc/supervisor.d/dnsmasq.conf" during parsing
2017-05-20 01:17:46,589 WARN Included extra file "/opt/docker/etc/supervisor.d/hhvm.conf" during parsing
2017-05-20 01:17:46,589 WARN Included extra file "/opt/docker/etc/supervisor.d/nginx.conf" during parsing
2017-05-20 01:17:46,589 WARN Included extra file "/opt/docker/etc/supervisor.d/postfix.conf" during parsing
2017-05-20 01:17:46,590 WARN Included extra file "/opt/docker/etc/supervisor.d/ssh.conf" during parsing
2017-05-20 01:17:46,590 WARN Included extra file "/opt/docker/etc/supervisor.d/syslog.conf" during parsing
2017-05-20 01:17:46,599 INFO RPC interface 'supervisor' initialized
2017-05-20 01:17:46,600 INFO supervisord started with pid 1
2017-05-20 01:17:47,602 INFO spawned: 'nginxd' with pid 16
2017-05-20 01:17:47,604 INFO spawned: 'hhvmd' with pid 17
-> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh
2017-05-20 01:17:47,613 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-20 01:17:47,613 INFO success: hhvmd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
-> Executing /opt/docker/bin/service.d/hhvm.d//10-init.sh
nginx: [emerg] open() "/docker.stdout" failed (13: Permission denied)
2017-05-20 01:17:47,648 INFO exited: nginxd (exit status 1; not expected)
Cannot open log file: /docker.stdout
2017-05-20 01:17:47,702 INFO spawned: 'nginxd' with pid 22
cap_set_proc failed
2017-05-20 01:17:47,705 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
-> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh
nginx: [emerg] open() "/docker.stdout" failed (13: Permission denied)
2017-05-20 01:17:47,748 INFO exited: nginxd (exit status 1; not expected)
2017-05-20 01:17:48,755 INFO spawned: 'nginxd' with pid 29
-> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh
2017-05-20 01:17:48,765 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
nginx: [emerg] open() "/docker.stdout" failed (13: Permission denied)
2017-05-20 01:17:48,779 INFO exited: nginxd (exit status 1; not expected)
2017-05-20 01:17:49,781 INFO spawned: 'nginxd' with pid 34
-> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh
2017-05-20 01:17:49,787 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
nginx: [emerg] open() "/docker.stdout" failed (13: Permission denied)
2017-05-20 01:17:49,801 INFO exited: nginxd (exit status 1; not expected)
2017-05-20 01:17:50,803 INFO spawned: 'nginxd' with pid 39
^C2017-05-20 01:17:50,805 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-05-20 01:17:50,805 WARN received SIGINT indicating exit request
2017-05-20 01:17:50,805 INFO waiting for nginxd, hhvmd to die
-> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh
nginx: [emerg] open() "/docker.stdout" failed (13: Permission denied)
2017-05-20 01:17:50,827 INFO exited: nginxd (exit status 1; not expected)
2017-05-20 01:17:50,828 INFO stopped: hhvmd (terminated by SIGTERM)
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 42 (21 by maintainers)
Can you please try to update your docker and docker-compose version and retry? Your version is quite old and you should try to stay up2date with docker.
BTW: an easier cron solution will be coming in the next days/weeks. We’re planing to replace the system cron with go-crond with better logging support and full environment variable support.
BTW: if this is a problem with an old docker verison we still should try to fix it. But we need a way to reproduce it