Error: Get ../podman.sock: connect: no such file or directory #7301
Comments
openshift-ci-robot
added
the
kind/bug
|
After installing podman (-remote) on your Mac, you need to set up the environment to point to your Linux server (with podman) Unfortunately there is no documentation for v2 yet, but something like: The documentation progress is here: #6830 |
|
I'm not really sure what Mac uses to administer* the built-in virtualization, but a VM with Fedora should be enough for podman... * Previously we used VirtualBox, but that has been deprecated. Other commercial alternatives include VMware and Parallels. https://fedoramagazine.org/install-fedora-virtualbox-guest/
|
|
I'm currently writing a blog on this but here is the short version.l You will need a linux server somewhere running sshd. Using an ssh key right now is required, but there is a PR upstream to fix this. On the server:
On the client.
This is from memory and in a rush. hopefully it helps until i can publish this thing. |
|
The blog has been published: https://www.redhat.com/sysadmin/podman-clients-macos-windows I'm going to go ahead and close this - please open a new bug with any further issues that arise with the new process. |
|
This seems like a limiting factor in terms of the adoption of podman. I wanted to use podman on mac to avoid the docker socket but if I'm required to have a linux VM this is even worse than the docker socket issue for a simple client setup. |
Podman is a Linux-only program. Hopefully this is now clear, from the new podman.io documentation ? If you want to discuss the availability of a Mac bundle, I would suggest the podman community meeting. |
|
To elaborate further, it's simply not technically possible to do containers
natively on OS X at the moment. The kernel features that containers rely on
(most notably process namespacing) are simply not available on OS X, and
Apple has shown no interest in adding them thus far. The model at this
point for both us and Docker is a native OS X binary capable of remotely
connecting to a server that actually launches containers (typically located
on a VM, but can also be on a remote server as well). Docker does package
things up quite neatly, but I assure you they are also doing Linux VMs for
local development on OS X.
…On Sun, Nov 22, 2020 at 3:32 PM Anders Björklund ***@***.***> wrote:
This seems like a limiting factor in terms of the adoption of podman. I
wanted to use podman on mac to avoid the docker socket but if I'm required
to have a linux VM this is even worse than the docker socket issue for a
simple client setup.
Podman is a *Linux-only* program. Hopefully this is now clear, from the
new podman.io documentation ?
With "Podman Machine" I *tried* to bring the support to 2015 standards,
but it failed - and is deprecated.
If you want to discuss the availability of a Mac bundle, I would suggest the
podman community meeting <https://podman.io/community/meeting/>.
On Windows you can use WSL, but there is no such built-in feature (i.e. a
Linux distribution) in macOS...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#7301 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCFSYJRCE6AMNAZR2UDSRFYMZANCNFSM4P32OO2Q>
.
|
|
Just bringing this up so you are aware users are still running into this. In general I think we should consider making the installation similar to Docker users just want it to work out of the box. I understand docker uses a VM that is not the point the problem is when a new user does: brew install podman It does not work. Thanks @afbjorklund I will look into joining the community meetings and see if I can bring some other key community members from the cloud-native space into this discussion. |
|
@peters95 : You can also continue to describe the requirement here: #8452 This old issue was more about the default error when not having a server, which is similar on Linux too: $ podman-remote version
Error: Get "http://d/v2.0.0/libpod../../../_ping": dial unix ///run/user/1000/podman/podman.sock: connect: no such file or directoryThe new issue is more about what are you are describing, how to bundle a Linux VM with a Mac version. Maybe have a Linux VM that exports a UNIX socket, the same way that https://web.archive.org/web/20171003123928if_/https://docs.docker.com/docker-for-mac/docker-toolbox/ When using |
|
Reading this issue I get that podman is Linux only. All that being said, assuming |
|
The error from "podman-remote" is similar on all platforms. But on mac/win, the binary is renamed to just "podman". Only excuse is that the output matches the one from the docker client. Maybe with a slightly less "friendly" wording ?
It also looks slightly different when running rootless, when compared to these "regular" (rootful?) socket locations. A friendly greeting could probably be added, but there still needs to be some documentation* on how to set up a VM... * the one you linked to doesn't work with podman v2, only varlink The podman.io documentation just assumes you know how to do it:
https://www.redhat.com/sysadmin/podman-clients-macos-windows
The "new approach" for this I was working with, uses Vagrant do it: https://www.vagrantup.com/intro Vagrant.configure("2") do |config|
config.vm.box = "generic/fedora32"
config.vm.provision "shell", privileged: false, inline: <<-SHELL
sudo yum install -y podman
systemctl enable --user podman.socket
systemctl start --user podman.socket
SHELL
end
I was going to "wrap" it in a more user-friendly script (replacing the deprecated docker-machine and podman-machine), https://boot2podman.github.io/2020/07/22/machine-replacement.html The other ticket was about a Mac bundle, using Hypervisor.framework https://developer.apple.com/documentation/hypervisor Then you wouldn't need Vagrant and Virtualbox, or set up the VM. It would be more like a "Podman Desktop", where it was integrated ? |
|
I have to with agree with others that podman needing another VM to handle the socket interface is an adoption barrier. Currently macos is my preferred dev env. I am using crc for openshift work as i want to interact with a local registry. This leaves me with giving up on podman and going to docker installed with the socket vm running as I DONT want to run another linux VM just so i can run podman commands to be able to jump to crc on my mac. Also as we are working with GKE and the gcloud client tools require something like docker as well to talk to registries....sorry just reality in 2021....I have resisted docker desktop for along time but i need to get my work done and i loved vagrant and vbox but support has moved to away from that as well... |
|
hang tight ... stuff on the very near horizon! |
|
This is now followed up in #8452 (the "friendly" error message was added in podman3) Initially it got caught up in the semantics of needing to run a virtual machine (currently a requirement on macOS), and knowing that the system is running a virtual machine "behind the scenes". Most people just want someone else to handle it for them, like "serverless". It might still run on a server somewhere, as long they can interact with the system without knowing or caring ? So this new Podman-for-Mac product could run Linux in a VM (just like Docker), as long as it offers a On an unrelated note, CRC was going to offer Podman Remote support directly (some time) |
|
FWIW, as a brand new user, I didn't understand why podman3 wasn't working on MacOS until I found this issue. I'll just paste the new "friendly" error message here for searchability. |
|
If you are on Mac and don't really need Podman you can use docker. |
Just can not find podman.sock file, type |
|
Sorry reading this thread through I still don't understand what to do to fix this? Getting the error same as @gth7754125 on May 26 and then can't use podman 3.2.2 for same reason. |
|
I'm in the same boat as @bentito . I don't see how to solve this. |
|
Please open a new issue describing your exact problem. |
|
done: #10944 |
github-actions
bot
added
the
locked - please file new issue/PR
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I installed podman on my macOS (High Sierra 10.13.6) using homebrew.
And it says that the podman was successfully installed!
But after I enter podman on the terminal, it gives me the following error
Steps to reproduce the issue:
brew cask install podman
podman
Describe the results you received:
Error: Get http://d/v1.0.0/libpod../../../_ping: dial unix ///var/folders/m5/s6r4jc2n683grgxld0r1hgch0000gn/T/run--1/podman/podman.sock: connect: no such file or directory
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:When I type 'podman version', it also shows the same error.
Output of
podman info --debug:Same here
Package info (e.g. output of
rpm -q podmanorapt list podman):Additional environment details (AWS, VirtualBox, physical, etc.):
I'm installing the podman on my Mac OS (High Sierra 10.13.6)
The text was updated successfully, but these errors were encountered: