Help understanding how the owner and group of bind mounts is set #25301
Unanswered
edumserrano
asked this question in
Q&A
Replies: 1 comment
-
Regarding question number 3, the only way I found to get the same behaviour was to set the automount.options in the Steps:
After the above steps, if I run a command with bind mount like I am however uncertain of side effects of doing this... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm a
docker desktop
user onWindows
and recently I've been trying to switch to usingpodman
. I've come across a difference betweenpodman
anddocker desktop
that I'd like some help understanding.If I run:
docker run --entrypoint /bin/sh -it -v ${PWD}:/app node:22.13.1
withpodman
and then inside the container I runls -la /app
I get the following:but if I run the same commands using
docker desktop
the results of thels -la /app
show the owner and group asroot
instead ofnode
.Furthermore, if I use a named volume with
podman
, then group and owner are set toroot
. For instance in a compose file:It seems that for, bind mounts,
podman
chowns the directories to the UID of the default user of the image ?Can someone help me understand:
podman
anddocker desktop
?podman
is different between bind mount and named volume ?podman
that I get withdocker desktop
? Meaning, in the above example, how can I get the user and owner of the bind mount for/app
to beroot
instead ofnode
?podman info
Also, in case it helps, here's the output of my podman info
Beta Was this translation helpful? Give feedback.
All reactions