-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
Docker root owned files #273
Comments
@Davincible what version of docker are you running in what OS? I too was seeing this message when trying to build a docker image for In my case this seemed to be because of strange behaviour from the I opened a ticket for this upstream: moby/moby#46161 If you are in the same situation as me I would suggest trying to run an upstream version instead and see if the problem is still there. |
On Manjaro, Docker 24. Fixed by creating a manual dockerfile:
|
Hmm I see... I am curious how the
It shows the directory as properly owned and with nothing inside it:
After running a docker version that was able to persist such ownership things seemed to work with no changes (and it seems to be ubuntu-related: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/2029564). I guess it would be interesting to revert your changes to the default and inspect if the permissions are not correct after user creation as I guess this is what would make npm sad in the later steps. |
Preflight checklist
Describe the bug
This happens for every clean build on latest
Reproducing the bug
Run container
Relevant log output
No response
Relevant configuration
No response
Version
latest
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered: