Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

NGINX cannot access basic auth data in /etc (nginx-ingress-controller:0.9.0-beta.1) #2403

Closed
evgf opened this issue Feb 22, 2017 · 3 comments

Comments

@evgf
Copy link

evgf commented Feb 22, 2017

Hello,
When upgrading the NGINX Ingress Controller image from v. 0.8.3 to v. 0.9.0-beta.1 (gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.1) we discovered that all our Ingresses using basic authentication do not work (HTTP 500).
The reason is that the auth data are stored in /etc/ingress-controller/auth but the privileges of the /etc directory were changed from 755 (in 0.8.3) to 750 (in 0.9.0 beta 1). The NGINX worker processes run as nobody and cannot open these files:

2017/02/22 09:45:01 [crit] 341#341: *11 open() "/etc/ingress-controller/auth/default-kibana.passwd" failed (13: Permission denied),

It seems that some work was invested into moving the NGINX-specific files under /ingress-controller but this does not cover the auth data and the new directory also has the 750 privileges.

@aledbf
Copy link
Contributor

aledbf commented Feb 22, 2017

@evgf this is already fixed in master and included in the next beta

@evgf
Copy link
Author

evgf commented Feb 22, 2017

Thank you @aledbf!
Do you know when the new image will be available?

docker pull gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.2
Pulling
repository gcr.io/google_containers/nginx-ingress-controller
Tag 0.9.0-beta.2 not found in repository gcr.io/google_containers/nginx-ingress-controller

@evgf
Copy link
Author

evgf commented Feb 22, 2017

Got it, thanks again!

@evgf evgf closed this as completed Feb 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants