-
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] Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory #4364
Comments
/remove feature |
You need to configure a Linux system to be accessible by podman for podman on MAC to work. |
@rhatdan It would be really helpful if you share some kind of doc reference of what you suggest |
@jwhonce is preparing such a document now. |
Did you managed to get a signed podman, my testing of podman got stuck at #4511 |
Nope, still not properly signed... |
FYI... In case you are using |
Hi, I've got stuck here too, any draft to share @jwhonce ? |
Would be interested in how to get podman running on macOS, too. Any hints? |
Same problem here. Waiting for you @jwhonce :) podman version 1.6.1-dev (installed with brew cask) |
Please post the link if its partially done too (to at least get podman working :) ) Thanks. |
waiting the document too :) |
I don't have access to Catalina, so these are my best guesses until I do:
Note that in the above example the macos user has provided the linux server with their ssh public key for access without a password. And yes, varlink is called twice. Once, for the ssh-tunnel the other is doing the actual work. I hope this helps. |
Got stuck here too
|
I have the same problem. |
I can give ssh access to a MacOS Catalina with latest xcode and homebrew if any libpod developer for debugging libpod building. I suspect that building podman for macos will be a real struggle if we build inside a linux vm code that later runs on macos. I bet is not possible to sign that binaries from within the linux vm. |
The same problem for me on a fresh macOS Catalina install with only Podman installed (with Very sad to not be able to replace the docker-cli with it now... |
The macOS catalina filesystem is mounted in a readonly partition. It looks like podman is triyng to set run time in this partition.
Installing version 1.6.3 i get a more
|
Podman expects /run to be mounted as a tmpfs and be writeable. |
It also expects it to contain a unix socket, which it probably wont. Exposing the socket file from the VM to the Mac host is a big hassle... Probably easier to just use the varlink protocol (over ssh) instead ? Seems like the original root cause is the missing environment variables. It needs the For instance: podman-machine env --varlink |
@jwhonce : did you complete any docs, on how to set up the Linux virtual machine ? Here is one link that I found: https://medium.com/@bszeti/podman-and-skopeo-on-macos-1b3b9cf21e60 It uses VirtualBox, to create a Fedora VM and then install ssh and podman packages. Similar to this setup: https://podman.io/blogs/2019/01/14/podman-machine-and-boot2podman.html |
@amitkrout I followed the instructions here and got it to work: But FYI export that env var for the link. I'm not sure why the doc shows it the way it does. |
@jwhonce, is this issue resolved with the latest updates to the docs? |
@TomSweeneyRedHat WDYT? |
Sure, always happy to take a PR. |
I hit the same issue, Is there any update for this issue?
|
I won't be able to provide a PR, I am hoping maintainers can jump in. |
We've had comments in containers/podman#4364 that it's unclear that we don't actually run Podman on Windows and Mac, rather it runs only on Linux and you need remote clients on the other platforms. This updates the whatis document to hopefully clarify. Signed-off-by: TomSweeneyRedHat <[email protected]>
We've had comments in containers/podman#4364 that it's unclear that we don't actually run Podman on Windows and Mac, rather it runs only on Linux and you need remote clients on the other platforms. This updates the whatis document to hopefully clarify. Signed-off-by: TomSweeneyRedHat <[email protected]>
Clarified (hopefully) in containers/podman.io#210 |
We've had comments in containers/podman#4364 that it's unclear that we don't actually run Podman on Windows and Mac, rather it runs only on Linux and you need remote clients on the other platforms. This updates the whatis document to hopefully clarify. Signed-off-by: TomSweeneyRedHat <[email protected]>
We've had comments in containers/podman#4364 that it's unclear that we don't actually run Podman on Windows and Mac, rather it runs only on Linux and you need remote clients on the other platforms. This updates the whatis document to hopefully clarify. Signed-off-by: TomSweeneyRedHat <[email protected]>
We've had comments in containers/podman#4364 that it's unclear that we don't actually run Podman on Windows and Mac, rather it runs only on Linux and you need remote clients on the other platforms. This updates the whatis document to hopefully clarify. Signed-off-by: TomSweeneyRedHat <[email protected]>
We've had comments in containers/podman#4364 that it's unclear that we don't actually run Podman on Windows and Mac, rather it runs only on Linux and you need remote clients on the other platforms. This updates the whatis document to hopefully clarify. Signed-off-by: TomSweeneyRedHat <[email protected]>
containers/podman.io#210 has merged fwiw |
Seems the issue has come back: https://stackoverflow.com/q/65590560/130638
I'm running Big Sur 11.1 (20C69) Here's my uname:
|
never mind, user error, hadn't yet configured the remote client connection: https://github.com/containers/podman/blob/master/docs/tutorials/mac_win_client.md |
Considering the number of users encountering this cryptic error, I would reopen this issue and assure that when we fail with it, we also print a descriptive message, maybe one with a link to documentation page. |
I'd also update https://podman.io/getting-started/ to have a section within As I think most people see installation part there, and be like, okay, nevermind, I've already got podman successfully installed via brew, so I don't need to look at that, and jump directly into the usage. |
Or just make the error message look like Docker, then everyone would recognize it ? #7301 (comment)
For what it is worth, it is the same story on Linux (when you run the same program,
|
How about |
Actually I like this better. |
For some people like me who couldn't really understand why For MacOS users can simply run these commands which install podman + virtual machine program(qemu) to spin up a linux VM.
|
Where should we document this to make it easier to understand? |
@ashley-cui @baude WDYT of adding a --now flag to podman machine init? systemctl enable --now foo.service Is what I base the idea on. Then the instructions could be simplified to |
i used below steps to resolve. Removed podman brew uninstall podman rm ~/.ssh/podman* related files |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
$ brew cask install podman
$ podman pull ubuntu
Describe the results you received:
Describe the results you expected:
should not throw runtime error
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
physical
The text was updated successfully, but these errors were encountered: