-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nginx configuration broken #79
Comments
Errrrrrr... on a second though, I think that my guess of where the bug is hiding may be wrong... I'm not an expert yet in docker and I let myself go with the excitement of the finding. Forget my guess, and focus on the fact that nginx configuration doesn't end in the folders it should. Regards, Angel |
Will you run with |
+1 here. After deploying the container throws endless errors about not finding the nginx.conf file: 7/23/2018 2:26:30 PM7/23/2018 2:26 nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file or directory) I tried with the tag mentioned above @hopsoft and that didn't change anything I'll try to pull the Dockerfile and add the working directory line mentioned above |
@hopsoft without making changes I built the container from the docker file in Master and that seems to be working. I wonder if the published one in the registry is just missing something? |
Perhaps so. I'll look at forcing a new build on Docker hub. |
Hi hopsoft,
I was installing your docker under FreeNAS Corral and it didn't work. Seemed permission stuff at the begining, as the nginx config dir was always empty no matter my efforts and tests, but following the leads I arrived to your page and I believe to have found the mistake in the Dockerfile.
After cloning the statsd git repo you're not changing the WORKDIR like with the other tools you're cloning, and that's why I believe that all the config gets screwed after that point.
Just my guess, if you could please look into it I'll be glad.
Regards, Angel
P.S: I imagine that only new installs suffer from this problem, as far as I've understood. Could have happened in the last build 5 days ago???
The text was updated successfully, but these errors were encountered: