Closed jmontleon closed 1 week ago
Trying with a clean Fedora 40 install and podman without machine the mount was owned by root:root and could not be written to. Trying a second clean install with podman-remote/machine it behaved the same, so it seems this behavior is the same on Fedora regardless of using podman machine.
Are you using docker-compose of podman-compose?
Could the ${PWD} be pointing at different directories when run from the Mac versus run from Fedora?
Is ${PWD} in the users homedir? If yes then the file system is shared over virtiofsd on the MAC, whereas it is just a bind mount on Fedora.
We are using podman-compose
.
When podman-compose
is run it is being done from within the git repo cloned in the users home directory, so ${PWD} is somewhere in the home directory on each host.
I tried on two separate clean Fedora 40 VM installs last night, one using podman-remote with a podman machine, one a local connection, and the permissions of the mount in both cases were root:root.
Well we don't directly support Podman-compose, but one thing you might try is to add a :U to your volume mount.
The :U suffix tells Podman to use the correct host UID and GID based on the UID and GID within the
container, to change recursively the owner and group of the source volume. Chowning walks the file
system under the volume and changes the UID/GID on each file. If the volume has thousands of inodes,
this process takes a long time, delaying the start of the container.
A friendly reminder that this issue had no activity for 30 days.
Since I never heard back, closing, reopen if I am mistaken.
Issue Description
Describe your issue We are using a compose file to start some containers. It is available here: https://github.com/konveyor/kai/blob/main/compose.yaml
Within the containers /podman_compose is being mounted rw so we can write logs.
On Mac we are seeing that the permissions for the directory are and the default user (id 1001) can write to the folder:
drwxr-xr-x. 34 default root 1088 Jul 29 18:33 /podman_compose
Meanwhile on Fedora Linux 40 it is mounted and the default user cannot write to it unless I using podman unshare to adjust permissions first:
drwxr-xr-x. 18 root root 4096 Jul 29 18:04 /podman_compose/
We're not sure why we are seeing different behavior and are trying to understand how to make both behave the same.
Steps to reproduce the issue
Steps to reproduce the issue
podman compose up
with the linkedcompose.yaml
on Fedorapodman compose up
with the linkedcompose.yaml
on MacDescribe the results you received
Differing volume permissions
Describe the results you expected
Identical volume permissions
podman info output
Mac
podman info --debug
output:Fedora 40
podman info --debug
output: