We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey, since updating to 0.16.0, we have:
2018/06/23 09:13:58 [crit] 1267#1267: *10412 connect() to unix:/tmp/prometheus-nginx.socket failed (13: Permission denied), context: ngx.timer, client: 10.10.22.180, server: 0.0.0.0:443 2018/06/23 09:13:58 [error] 1267#1267: *10412 lua entry thread aborted: runtime error: /etc/nginx/lua/monitor.lua:10: permission denied stack traceback: coroutine 0: [C]: in function 'assert' /etc/nginx/lua/monitor.lua:10: in function 'func' /etc/nginx/lua/util/defer.lua:19: in function </etc/nginx/lua/util/defer.lua:9>, context: ngx.timer, client: 10.10.22.180, server: 0.0.0.0:443
Guessing this is something to do with removing non-root?
Looking at the the container, that folder appears to be owned by root:
-rw-r--r-- 1 www-data www-data 2.2K Jun 21 21:06 koi-win drwxrwxr-x 5 root root 4.0K Jun 22 18:35 lua -rw-r--r-- 1 www-data www-data 5.1K Jun 21 21:06 mime.types
Which i don't think the issue actually is, I believe it's due to:
root@ingress-nginx-internal-controller-56d99ffc44-sbfmn:/etc/nginx# ls -lah /tmp total 24K drwxrwxrwx 1 root root 4.0K Jun 23 10:19 . drwxr-xr-x 1 root root 4.0K Jun 23 10:18 .. drwx------ 2 nobody root 4.0K Jun 23 10:19 client-body drwx------ 2 nobody root 4.0K Jun 23 10:19 fastcgi-temp -rw-r--r-- 1 root root 3 Jun 23 10:19 nginx.pid srwxr-xr-x 1 root root 0 Jun 23 10:19 prometheus-nginx.socket
The text was updated successfully, but these errors were encountered:
Ahh We needed to update our custom helm chart to be:
ingress-nginx/test/manifests/ingress-controller/mandatory.yaml
Line 261 in 306910d
I'd imagine others are going to get caught out by this! Might want to add something prominent in the upgrade docs.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Hey, since updating to 0.16.0, we have:
Guessing this is something to do with removing non-root?
Looking at the the container, that folder appears to be owned by root:
Which i don't think the issue actually is, I believe it's due to:
The text was updated successfully, but these errors were encountered: