-
Notifications
You must be signed in to change notification settings - Fork 77
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 problem? #71
Comments
Hi there 👋 We are having the same issue since someone has override the 3.3.2-nginx image tag Our current workaround is to use a previous image digest form the IMO the published tags should not be overridden |
Same problem here !!! |
Definitely a bad idea to overwrite the tag! Thank you for the workaround, I will try it when I have time. |
Thanks for reporting this. I noticed the same today by chance. We'll look into it. |
An issue with this image was fixed in #62. Can you force pull and check whether your issue persists? |
EDIT: I am dumb, when you said it was addressed I thought you meant it was solved. I see that the issue is still open though. |
Sorry. I meant to write that overwriting of image tags should be addressed by #67. |
Hello, I am doing a university project and I was advised to use this container. I thought it was working fine, but tonight when I tried it and I accessed the modsecurity port, I got this:
So I tried using a very very simple docker-compose.yml (please check if I have made any mistakes in the compose file):
I still get the same response from modsecurity (port 8000), while whoami works fine (port 80).
Here are the modsecurity logs, but I think they are useless:
I tried entering the container to read the /var/log/nginx/error.log but cat does not seem to work and there are no tail, nano or vi installed.
EDIT: I know this might be a mistake on my part in configuring the container, sorry if that is the case.
The text was updated successfully, but these errors were encountered: