Podman: [macOS] Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory

Created on 29 Oct 2019 · 32Comments · Source: containers/podman

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:

$ podman pull ubuntu
Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory

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:

$ podman version
Client:
Version:            1.6.1-dev
RemoteAPI Version:  1
Go Version:         go1.12.9
OS/Arch:            darwin/amd64

Service:
Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory

Output of podman info --debug:

$ podman info --debug
Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory

Package info (e.g. output of rpm -q podman or apt list podman):

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):
physical

kinbug

Source

amitkrout

Most helpful comment

@rhatdan It would be really helpful if you share some kind of doc reference of what you suggest

amitkrout on 29 Oct 2019

👍21 😄2

All 32 comments

/remove feature

amitkrout on 29 Oct 2019

You need to configure a Linux system to be accessible by podman for podman on MAC to work.

rhatdan on 29 Oct 2019

@rhatdan It would be really helpful if you share some kind of doc reference of what you suggest

amitkrout on 29 Oct 2019

👍21 😄2

@jwhonce is preparing such a document now.

rhatdan on 30 Oct 2019

👍7

Did you managed to get a signed podman, my testing of podman got stuck at https://github.com/containers/libpod/issues/4511

ssbarnea on 14 Nov 2019

Did you managed to get a signed podman, my testing of podman got stuck at #4511

Nope, still not properly signed...

ag1989 on 14 Nov 2019

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 macOS Catalina
https://developer.apple.com/news/?id=09032019a

amitkrout on 26 Nov 2019

👍1

Hi, I've got stuck here too, any draft to share @jwhonce ?
Thanks !

zekaguilar on 29 Nov 2019

Would be interested in how to get podman running on macOS, too. Any hints?

MrBuddyCasino on 4 Dec 2019

Same problem here. Waiting for you @jwhonce :)

podman version 1.6.1-dev (installed with brew cask)
macOS Catalina 10.15.1

guiguir68 on 4 Dec 2019

@jwhonce is preparing such a document now.

Please post the link if its partially done too (to at least get podman working :) )

Thanks.

sachingorade on 5 Dec 2019

👍4

waiting the document too :)

misanche on 10 Dec 2019

I don't have access to Catalina, so these are my best guesses until I do:

# xattr -d com.apple.quarantine /usr/local/bin/podman
Or,
# xattr -d com.apple.quarantinereadlink /usr/local/bin/podman
should get you over the signing issue. Then setting PODMAN_VARLINK_BRIDGE to point to your linux server.

$ export PODMAN_VARLINK_BRIDGE=$'ssh -T -p22 root@localhost -- "varlink -A \'podman varlink \$VARLINK_ADDRESS\' bridge"'

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.

jwhonce on 10 Dec 2019

Got stuck here too

Client:
Version: 1.6.1-dev
RemoteAPI Version: 1
Go Version: go1.12.9
OS/Arch: darwin/amd64
Service:
Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory

zhuguoliang on 24 Dec 2019

I have the same problem.

lokinell on 24 Dec 2019

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.

ssbarnea on 25 Dec 2019

The same problem for me on a fresh macOS Catalina install with only Podman installed (with brew cask).

Very sad to not be able to replace the docker-cli with it now...

davinkevin on 2 Jan 2020

The macOS catalina filesystem is mounted in a readonly partition. It looks like podman is triyng to set run time in this partition.

$ sudo mkdir -p /run/podman
mkdir: /run/podman: Read-only file system

Installing version 1.6.3 i get a more

Client:
Version: 1.6.3-dev
RemoteAPI Version: 1
Go Version: go1.12.10
Git Commit: 6c6e78374f5be949d11a8608080c96e2d22ca872
Built: Tue Oct 29 20:08:11 2019
OS/Arch: darwin/amd64

Service:
Error: error creating libpod runtime: dial unix /run/podman/io.podman: connect: no such file or directory

andreufontb on 3 Jan 2020

Podman expects /run to be mounted as a tmpfs and be writeable.

rhatdan on 4 Jan 2020

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...
Docker does this *, but I'm not sure that Podman has the same need.

Probably easier to just use the varlink protocol (over ssh) instead ?

Seems like the original root cause is the missing environment variables.
Without the remote config, it will assume it is running on a Linux host.

It needs the PODMAN_VARLINK_BRIDGE set up

For instance: podman-machine env --varlink

afbjorklund on 4 Jan 2020

@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.

afbjorklund on 4 Jan 2020

@amitkrout I followed the instructions here and got it to work:
https://github.com/containers/libpod/blob/master/docs/tutorials/remote_client.md

But FYI export that env var for the link. I'm not sure why the doc shows it the way it does.

ipbabble on 21 Jan 2020

@ipbabble https://github.com/containers/libpod/pull/4997 updates the documentation for setting up the varlink bridge.

jwhonce on 28 Jan 2020

@jwhonce, is this issue resolved with the latest updates to the docs?

vrothberg on 31 Jan 2020

I hate to say I came here with exact same problem after reading website and poking through the CLI for 15 minutes.

Can someone please update podman.io homepage to say:

Podman only works on Linux, however a remote Linux machine can be configured from macOS and Windows to use Podman on other platforms.

ahmetb on 24 Mar 2020

👍8

@TomSweeneyRedHat WDYT?

vrothberg on 24 Mar 2020

Sure, always happy to take a PR.

TomSweeneyRedHat on 24 Mar 2020

I hit the same issue, Is there any update for this issue?

➜  ~ podman version
Client:
Version:            1.6.1-dev
RemoteAPI Version:  1
Go Version:         go1.12.9
OS/Arch:            darwin/amd64

Service:
Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory

Aisuko on 28 Mar 2020

I won't be able to provide a PR, I am hoping maintainers can jump in.

ahmetb on 28 Mar 2020

Clarified (hopefully) in https://github.com/containers/podman.io/pull/210

TomSweeneyRedHat on 28 Mar 2020

containers/podman.io#210 has merged fwiw

TomSweeneyRedHat on 16 Apr 2020

still have same issue with this Mac:

should i upgrade ? or is it podman issue ?

➜  ~ podman version
Error: Get "http://d/v2.0.0/libpod/_ping": dial unix ///var/folders/4s/ch8k_58x04l59gv_p4jfq6lr0000gn/T/podman-run--1/podman/podman.sock: connect: no such file or directory