-
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
Need podman to mount symbolic links for docker compatibility #20350
Comments
@ashley-cui @baude I think this is specific to Mac. |
if you ssh into the machine, does it look correct? I'm wondering if 9P does not honor it? |
No, when ssh'ed into the podman machine, there is no /store directory listed, however other symbolic links are shown:
What I see from the command line:
|
inside the machine, does |
Yes, of course. As stated in the initial problem statement, I can start the container mounting ~/store/pipeline but not using /store/pipeline because /store is created using /etc/synthetic.conf and while it appears as a symbolic link in ls I gather it must be different since podman doesn't see it. |
the problem here is how the mount between host and virtual machine is working. by default, we mount /Users/ to /Users/name on the virtual machine. In your case, you have a symlink at the root (/) level. But the host's / is not being shared into the virtual machine so it does not resolve. does it work if you do something like:
|
Yes, that worked. Thank you. Is there a way to make the machine initialize this way all the time (e.g., if I reboot)? |
You can add the mounts to containers.conf file.
|
Issue Description
I have used /etc/synthetic.conf to create a symbolic link off root to a directory in my home directory. The net effect is to have:
as specified by the following (note: there is a tab separating the data in /etc/synthetic.conf:
If I attempt to mount /store/pipeline using -v in the podman run command as follows:
It fails with
Error: statfs /store/pipeline: no such file or directory
even though the data are there (/store just is a symlink directory).Steps to reproduce the issue
Steps to reproduce the issue
cd ~ ; mkdir -p store/pipeline
ls -l / |grep store
Describe the results you received
Error: statfs /store/pipeline: no such file or directory
And the container does not run
Describe the results you expected
The container runs without issue and the contents of /store/pipeline are visible in the container.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
See details for setting up /store -> ~/store above
Additional information
This happens without fail. It is an incompatibility with docker. We need this to handle shell scripts used to start containers on various systems where additional disk space has been mounted off the root directory.
The text was updated successfully, but these errors were encountered: