-
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
Wrong file ownership on volumes initialized from container image #7130
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
Categorizes issue or PR as related to a bug.
label
Jul 29, 2020
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Jul 30, 2020
keep the file ownership when chowning and honor the user namespace mappings. Closes: containers#7130 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
PR here: #7164 |
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Jul 31, 2020
keep the file ownership when chowning and honor the user namespace mappings. Closes: containers#7130 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Jul 31, 2020
keep the file ownership when chowning and honor the user namespace mappings. Closes: containers#7130 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Jul 31, 2020
keep the file ownership when chowning and honor the user namespace mappings. Closes: containers#7130 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> <MH: Fixed conflicts from cherry pick> Signed-off-by: Matthew Heon <matthew.heon@pm.me>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Aug 17, 2020
keep the file ownership when chowning and honor the user namespace mappings. Closes: containers#7130 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> <MH: Fixed conflicts from cherry pick> Signed-off-by: Matthew Heon <matthew.heon@pm.me>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Aug 17, 2020
keep the file ownership when chowning and honor the user namespace mappings. Closes: containers#7130 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> <MH: Fixed conflicts from cherry pick> Signed-off-by: Matthew Heon <matthew.heon@pm.me>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 23, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
Description
The bind-mounted, freshly initialized volume contains correct files from the original
container image - but wrong permissions, when some directory has
rwx------
permissions.
Steps to reproduce the issue:
Describe the results you received:
You can see in that output that file ownership differs in the two
podman run
scenarios,one run with
-v
and one without.Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Normal F32 x86_64 native box.
The text was updated successfully, but these errors were encountered: