podman: In MacOS, latest version(1.5.1) of podman can't pull images.
/kind bug
Description In MacOS, latest version(1.5.1) of podman can’t pull images.
Steps to reproduce the issue:
-
In MacOS console, run “brew cask instal podman”
-
do a pull to see the issue
Describe the results you received: here is the result: bogon:Downloads test$ podman pull quay.io/openshift-release-dev/ocp-release@sha256:c28afba66cc09233f7dfa49177423e124d939cf5b0cd60d71bbb918edb0ed739 Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory
Describe the results you expected: I can pull images by podman
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
bogon:Downloads test$ podman version
Client:
Version: 1.5.1
RemoteAPI Version: 1
Go Version: go1.12.2
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:
bogon:Downloads test$ podman info --debug
Error: could not get runtime: dial unix /run/podman/io.podman: connect: no such file or directory
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 24 (18 by maintainers)
Personally I find this disappointing. MacOS is a primary dev environment in many organizations and podman is being advertised as a
painlesstransition from docker CLI.Having developer from only having to
install Docker for MacOSto havinginstall podman(via brew) andmanaging your own VM with remote connectionis a terrible developer experience and will limit the adoption rate of this tool.I strongly urge you guys review as IMO this is not a good product direction to continue.
Docker requires the same VM, it is not doing anything with MAC Containers. There is not difference. From a usability point of view, Boot2Docker and DockerMachine is better. Although opensource teams are working on Boot2Podman and we hope to get better integration with CRC (Code Ready Containers) for OpenShift integration. We continue to work on MAC and Windows support and are always looking for contributors to help accelerate the movement.
Here’s a brief write up: @gaord
Hi! So in order to use the the podman client on mac, currently, you have to have a linux machine running somewhere. It could be a vm or another physical machine. In order to connect to it, you can use environment variables, flags, or the podman-remote.conf file.
To connect using flags, you can use
podman --remote-host linux-ip --username rootTake a look at podman-remote.conf.5.md on how to use the conf file.Your linux IP can be determined using
ip addrIt’s probably the best if you use --username root. To do you this you may need to edit your /etc/ssh/sshd_config in your linux machine:
PermitRootLogin yesIn order to avoid ‘logging in’ every time you run a podman command, you may need to edit your /etc/ssh/sshd_config in your linux machine as follows:
You may also need to scp ssh keys from your mac to your linux host (from Mac ~/.ssh/id.pub in /root/.ssh/authorized_keys)
In order to connect, make sure your linux machine has podman installed on it, and run
Then, you can use podman as you usually do, with the podman-remote.conf file populated or use it with flags:
podman --remote-host linux-ip --username root COMMAND@ashley-cui Lets make a mac_client.md
Podman is a tool for running, building, manageing LINUX containers. Not MAC containers. In order to run a Linux Container you need a Linux kernel. On Windows they have added WSL to make people think that linux containers are running natively. But really under the covers they are just running a builtin VM.
Bottom line, unless MAC decided to build and support OCI based containers with an OCI based image, then you need a VM.
A small addendum, but I would strongly recommend use SSH key authentication, as opposed to allowing passwordless root login - much safer