-
Notifications
You must be signed in to change notification settings - Fork 618
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
podman sock not working in Fedora 41 image (rootful mode) #3038
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Fedora 41 (Lima v1.0.2): $ limactl shell podman-rootful curl --unix-socket /run/podman/podman.sock http://foo/_ping
curl: (7) Failed to connect to foo port 80 after 0 ms: Could not connect to server
$ limactl shell podman-rootful sudo curl --unix-socket /run/podman/podman.sock http://foo/_ping
OK
$ limactl shell podman-rootful ls -l /run/podman/podman.sock
ls: cannot access '/run/podman/podman.sock': Permission denied
$ limactl shell podman-rootful sudo ls -l /run/podman/podman.sock
srw-rw----. 1 root root 0 Dec 25 16:13 /run/podman/podman.sock Fedora 40: $ limactl shell podman-rootful-f40 curl --unix-socket /run/podman/podman.sock http://foo/_ping
OK
$ limactl shell podman-rootful-f40 ls -l /run/podman/podman.sock
srw-rw----. 1 suda suda 0 Dec 25 16:18 /run/podman/podman.sock Something seems wrong in: lima/templates/podman-rootful.yaml Lines 32 to 46 in 5fb9353
|
Fedora 41:
Fedora 40:
|
This should have been fixed with the previous commit ab544b5 Red Hat's installation of podman (or docker) requires connecting to the VM as root@ (or using sudo), for rootful... So not only did we keep the older pre-installed version, we also kept the original configuration (no lima overrides) Podman Desktop has the same issue (can't connect), by the way. |
Description
Podman sock isn't working in podman-rootful template having Fedora 41 image in my Mac M1 pro.
Steps to reproduce:
Workaround:
Updated the following image in template and everything is working fine.
The text was updated successfully, but these errors were encountered: