![]() I’ve not compiled any docker applications myself, as I lack the skill to do so, and maybe this is not related, but it seemed suspicious, so I thought I would report it here. If I ls the /run directory on either of the containers in question, I notice this is no nginx directory, AND the ngix.pid file is actually in the root of /run. This could be implemented via inotifywait and be enabled only optionally. This is the PID file mentioned in the error above. It would be helpful if nginx automatically reloads its config once a config file is changed. The interesting bit is that last argument for PID path: -pid-path=/run/nginx/nginx.pid. This is additional output past the dots, but I removed it for the sake of readability. If I connection to a bash shell session and print version information with nginx -V (big V), I get the following $ docker exec -it reverse-proxy nginx -VĬonfigure arguments: -prefix=/var/lib/nginx -sbin-path=/usr/sbin/nginx -modules-path=/usr/lib/nginx/modules -conf-path=/etc/nginx/nf -pid-path=/run/nginx/nginx.pid… I instances of each running on separate servers. This is true in both the linuxserver/nginx:latest and linuxserver//letsencrypt containers. Nginx: configuration file /etc/nginx/nf test failed Nginx: open() “/run/nginx/nginx.pid” failed (2: No such file or directory) Nginx: the configuration file /etc/nginx/nf syntax is ok I’ve noticed if I attempt to check config files or reload the nginx service with a docker exec command, I receive the following $ docker exec -it reverse-proxy nginx -t Now, the reason for my post I’m by no means and programmer or developer, but I think I stumbled across a bug in the nginx docker build. Hello all! I’m new to Docker and LinuxServer.io, but I’ve loving both already! The folks at Linux Server really have done a great job of documenting their containers and adapting them for all the popular architectures. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |