podman: On Mac OS Big Sur & Monterey podman machine starts but doesn't connect

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

brew installed podman on my Mac OS laptop properly. podman init also downloaded fedora image and created podman machine. However podman start remains at Waiting for VM prompt forever.

Steps to reproduce the issue:

  1. brew install podman

  2. podman machine init --disk-size 100 --cpus 4 --memory 4

  3. podman machine start

 $ podman machine start
INFO[0000] waiting for clients...                       
INFO[0000] listening tcp://127.0.0.1:7777               
INFO[0000] new connection from  to /var/folders/bx/gd38cjwd69g74tzf5p042xq40000gn/T/podman/qemu_podman-machine-default.sock 
Waiting for VM ...

Describe the results you received:

Refer above.

Describe the results you expected:

It should not hang forever. It should come out and connect.

Additional information you deem important (e.g. issue happens only occasionally):

Also following commands should do same.

Besides that podman machine stop should stop this zombie machine. It doesn’t show anything and doesn’t stop. podman machine rm fails too. So there is no way but to restart laptop to reset status of this podman machine.

 $ podman machine ssh
Connecting to vm podman-machine-default. To close connection, use `~.` or `exit`
kex_exchange_identification: Connection closed by remote host
Error: exit status 255

 $ podman system info
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: Connection to bastion host (ssh://core@localhost:49261/run/user/1000/podman/podman.sock) failed.: ssh: handshake failed: read tcp [::1]:49822->[::1]:49261: read: connection reset by peer

 $ podman info
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: Connection to bastion host (ssh://core@localhost:49261/run/user/1000/podman/podman.sock) failed.: ssh: handshake failed: read tcp [::1]:49826->[::1]:49261: read: connection reset by peer

Output of podman version:

 $ podman version
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: Connection to bastion host (ssh://core@localhost:49261/run/user/1000/podman/podman.sock) failed.: ssh: handshake failed: read tcp [::1]:49847->[::1]:49261: read: connection reset by peer

Output of podman info --debug:

 $ podman info --debug
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: Connection to bastion host (ssh://core@localhost:49261/run/user/1000/podman/podman.sock) failed.: ssh: handshake failed: read tcp [::1]:49851->[::1]:49261: read: connection reset by peer

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

N.A. Mac OS so apm / rpm not there.

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

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

Mac OS Laptop. Big Sur.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 32 (11 by maintainers)

Commits related to this issue

Most upvoted comments

carl, i think you might be exceeding the max length of filenames for sockets in macos… can you try:

podman machine init test podman machine start test ` and see if this is any better?

@xsa can you check the following:

  1. Does /Users/<my user>/.local/share/containers/podman/machine/podman-machine-default/ exist?
  2. Is there any stale qemu processes running (e.g. ps -ef | grep qemu)
  3. When you do a podman machine rm; podman machine init, do you get any errors there, or is it successful?
  4. When you run podman machine start and get the EINVAL, is there a qemu process running afterwords?