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
UID mismatch causes permission issues #8
Comments
Thanks for reporting this and sorry for the slow response. That's a good point. I've now made a note about this assumption in the article. I've hit this UID mismatch problem a few times in other contexts, but I have never come up with any particularly good solution. When I create the There is an issue on docker for this, moby/moby#7198, which it seems has been closed as fixed with moby/moby#20262, but it does not seem that it is actually fixed, given comments in e.g. docker/compose#3715. |
Thanks for the pointers. Guess I'll be going through the documentation to see if something useful has popped into existence. Stuff changes so fast 😩 BTW, I've been wondering whether In the mean time I'm working around by simply editing |
Using the gid approach assumes that you have a umask that doesn't remove group write permission, i.e. something like |
Hi, I was following through your really nice article and that went swell. Next, I tried repeating this with
node:6.10.0
. I checked out01-bootstrapping
and modified theDockerfile
'sFROM
statement to usenode:6.10.0
. Randocker-compose up
without a hitch. NextThing is, the newer
node
images have anode
user account (UID 1000). Creating a newapp
user (gets UID 1001) is fine, but when you run with that this no longer matches the UID outside the container. It looks to me that your article relied on the fact that your UID outside the container is the same as the UID of the user inside the container. You should probably mention that (and point to a fix if you know of one 😉).The text was updated successfully, but these errors were encountered: