[2623668873] Upstream Reporter: Vladimir Lazar
Upstream issue status: Closed
Upstream description:

Issue Description

It seems that the podman machine will get stuck in STARTING state permanently if the user interrupts the startup sequence one time. The entire system requires to be restarted or the podman machine needs to be deleted to recover from this. This issue was initially reported in PD repo https://github.com/containers/podman-desktop/issues/9670.

https://github.com/user-attachments/assets/3a0527db-c397-47a1-a290-6b9b0b72bf28

Steps to reproduce the issue

Steps to reproduce the issue

1. Create a new podman machine using podman machine init command
2. Start the podman machine created at point 1 using podman machine start command
3. Quickly after issuing the command from point 2 send CTRL-C command to the terminal (SIGINT) to terminate the operation.
4. Run podman machine ls and notice that the podman machine created at point 1 will be permanently stuck in STARTING state.

Describe the results you received

Podman machine is stuck permanently in STARTING state.

Describe the results you expected

Presumably the state of the podman machine should be Stopped or alternately Running if the SIGINT is not sent fast enough to prevent the startup. Regardless of the state of the podman machine it should not be frozen execute commands correctly afterwards.

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting