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
netbox user uid 101 Permission denied: '/etc/netbox/config/configuration.py' #298
Comments
Did you upgrade from a previous version or was this a vanilla installation?
Because it does not matter, does it? As far as I understand Linux the username is a convenience for us humans to work with the system. On the system level it works with user id's. You can set file permissions for any arbitrary (valid) user id. We've chosen this approach because it has the least impact and is the most flexible solution. For example OpenShift assigns your container a "random" user id anyway (which is |
This was on a fresh install (multiple users ran into this issue and mitigated it by dropping uid in |
@jkldgoefgkljefogeg I've just tried to use a freshly installed netbox (sha256:0b27442b40c38415523580aff3a65f2da4cee77d21d7065e1f37812873a5c22e, which corresponds to the latest tag at the moment) and didn't see any issues with the file permissions. As for the UID, +1 to @cimnine 's reply - whenever possible, software should be able to work with an arbitrary user id. That's true for both OpenShift and K8s with Pod Security Policies enabled.
|
I absolutely hate seeing docker containers that require root or being started with a specific user. Docker provides facilities for changing the user, and there's no reason a docker container needs to bind to root-only ports; the user can forward them to the real port. |
I'm closing this issue as it seems not to be a problem for most, respectively that the current solution is even the preferred solution for those that cared to comment. |
I guess this is why I got permission error with uid 101, not sure how it got into such a state
|
Found the workaround in #447 |
7942e9e broke volume permission. I had to drop
user: '101'
to work around this.Why use an arbitrary UID instead of a pre-created user?
-->
Current Behavior
Expected Behavior
no filesystem permission error
Debug Information
The output of
docker-compose logs netbox
:this was also reported in https://networktocode.slack.com/archives/CD23LP8BC/p1589066827266200
The text was updated successfully, but these errors were encountered: