Replies: 8 comments 1 reply
-
With the current version (4.0.3), |
Beta Was this translation helpful? Give feedback.
-
The default in 4.1 will be -v $HOME:$HOME |
Beta Was this translation helpful? Give feedback.
-
Oh, thanks a lot! Somehow I missed that. |
Beta Was this translation helpful? Give feedback.
-
While this was supposed to be fixed by newer versions of poadman that include $HOME in default machine mounts, for some reason with podman 4.4.2, it happens again, even if the machine was just recreated.
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Important aspect to check for, In my case I had the 4.4.2 client with 4.4.1 machine and it was giving this error. I destroyed the machine and recreated it and it magically started to work. I fixed it by running init without any extra arguments, and we should ensure that no extra options are needed. That is not the first time when I encounter a bug like this but I am not sure what we can do to improve the experience. |
Beta Was this translation helpful? Give feedback.
-
Not sure if this helps anyone, but if it's useful I'll share: I downloaded the new Podman Desktop, and started a podman machine via the GUI. For the life of me, I couldn't find out why local mounts were not working correctly. Everything appeared as expected, but it just didn't click. It wasn't until I went into the CLI and remove the machine, then recreated the machine, did it start working correctly again. I didn't really expect it to work (or I would have taken more notes), but let me send what I can/had in front of me at the time:
So all is good now. Again, not sure if any of this is helpful (it's definitely not new), but at least it's one more voice for "things just seemed to work, after first having some trouble." |
Beta Was this translation helpful? Give feedback.
-
When updating podman desktop now to v1.19.2 I had this error. Had to delete my machine with all my containers and images in it. Worked finally thank you. But I think I should not need to delete all of my previous work. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
It fails to bind local directory on MacOS.
Steps to reproduce the issue:
On macOS, run
podman machine init
andpodman machine start
Create directory (
~/git/podman-test
on my example)Try to run podman binding that directory as a volume:
podman run -it --rm --name hewwo -v ~/git/podman-test:/usr/src/hewwo -w /usr/src/hewwo python:3 python hewwo.py
Describe the results you received:
$ podman run -it --rm --name hewwo -v ~/git/podman-test:/usr/src/hewwo -w /usr/src/hewwo python:3 python hewwo.py Error: statfs /Users/bilko/git/podman-test: no such file or directory
Describe the results you expected:
Binding works, such as with docker:
$ docker run -it --rm --name hewwo -v ~/git/podman-test:/usr/src/hewwo -w /usr/src/hewwo python:3 python hewwo.py Hewwo wowld
Additional information you deem important (e.g. issue happens only occasionally):
I have permissions to access this directory (my user is bilko):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical Intel Mac Mini running macOS Monterey 12.3.1.
qemu version:
Beta Was this translation helpful? Give feedback.
All reactions