-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Volumes always owned by root #2634
Comments
What did the Dockerfile look like that created that image? |
It's there:
|
@neVERberleRfellerER Any chance you could build from master and see if this fixes the is you were seeing. |
@rhatdan I compiled your volumes branch on Arch Linux (I don't know how to build packages on Fedora) and there are 2 problems:
I can't rule out some kind of mistake on my side (actually, probability of such is very high). |
Sorry I fixed the path, probably should have waited for it to pass tests. :^( |
Now it works perfectly! |
Fixed by #2643 . |
/kind bug
Description
Volumes are always owned by root instead of inheriting owner and group from image.
Steps to reproduce the issue:
(ipfs used as example, but it happens with other images too)
1.
podman run --rm -it --entrypoint /bin/sh ipfs/go-ipfs
use
ls -laF /data
in container,see that volume is owned by root
Describe the results you received:
drwxr-xr-x 2 root root 4096 Mar 13 20:36 ipfs/
ipfs failing on permission denied
Describe the results you expected:
drwxr-xr-x 2 ipfs users 4096 Mar 13 20:28 ipfs/
ipfs working
Additional information you deem important (e.g. issue happens only occasionally):
Perfectly reproducible.
Output of
podman version
:Output of
podman info --debug
:Additional environment details (AWS, VirtualBox, physical, etc.):
physical, KVM. Happens on Fedora Silverblue, Fedora Atomic (with podman 1.0.0) and Arch Linux (without fuse-overlayfs).
The text was updated successfully, but these errors were encountered: