-
Notifications
You must be signed in to change notification settings - Fork 1.2k
uid collision on Centos 7 host #251
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
Comments
One solution that will work the most generically is to look into Docker's User Namespaces support to see if it's a fit for your use case (which would allow you to remap the user directly as desired), but barring that, you'll likely be interested in #253. 👍 |
great responsiveness.. thanks! 👍 |
I don't fully understand the solution. @dangogh what did you end up doing? |
I ended up in the entrypoint script adding this bash function which sets the owner of the subdir I created to be the same as the volume I had mounted:
|
Alright. Thanks for the response. Not happy with the hacky solution. |
neither am I -- one hack on top of another, but sometimes it's what you can do |
The hard-coded uid=999 value conflicts with the systemd-bus-proxy user on CentOS 7
This makes it difficult to use a volume mapped to a host directory as it is owned by the above user. Is there a recommended way to handle this?
The text was updated successfully, but these errors were encountered: