-
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
macos: podman fails to mount folders from another partition: statfs ... no such file or directory #23967
Comments
That was the first thing I tried once i discovered the issue. Yep, it does not mount:
|
Based on my research it seems that by default podman machine is not created with volume mounts needed for properly mount code from macos.
I am going to follow their recommendation and test the I know that they could in theory use other location for mounting, but that is highly unlikely, due to how macos works. Results: it works. @baude Should we rename this issue to mark changing default volume mount on macos? -- That is quite important especially from UX point of view, as we do want a setup that "just works". |
A friendly reminder that this issue had no activity for 30 days. |
This post has saved me from ripping all my hair out. I had to add the /tmp directory to it as well, but this worked for me.
|
Issue Description
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
Podman should be able to mount local partitions.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
$ uname -a
Darwin m1 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000 arm64
Additional information
It should be noted that the partition that I am an APFS Volume created with case-sensitive switch on, because that is recommended for keeping code that works on linux (default APFS is case insensitive).
I am not sure yet if that case-insensitive is the cause for failure or any kind of partition would trigger the same bug.
Initially I believed it was the fact that this partition is symlinked to
~/code
location and that this might confuse PWD, but I tried resolving the path and the issue is still present.statfs reports it as not being able to find it.
I also destroyed and recreated the podman machine as part of debugging, no change in behavior. Out of curiosity I also tested docker behavior, but docker does not seem to have any problem mounting it.
The text was updated successfully, but these errors were encountered: