-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 machine gets stuck in STARTING state if interrupted during startup #24416
Comments
Your video does not work for me. Please post an actual log or transcript. Why do you call this a race? On your fourth point, you say "will not be permanently stuck" and I think you mean to say "will be"? Can you confirm this and update what you are trying to show in the video? You also need to provide |
@baude in what way is the video not working for you? I just watched it again, works fine, have you tried a different browser? About point 4, you are correct, there was a not that should not have been, I've edited the post. |
Attached the output from |
UPDATE: I've also managed to reproduce the issue on macOS today, so it's not limited to Windows only. |
when i click the video, it doesnt play. either way, we prefer people post text things where possible as opposed to binary objects. |
The text is that after |
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 podman-desktop/podman-desktop#9670.podman_start_race_condition.mp4
Steps to reproduce the issue
Steps to reproduce the issue
podman machine init
commandpodman machine start
commandCTRL-C
command to the terminal (SIGINT) to terminate the operation.podman machine ls
and notice that the podman machine created at point 1 will be permanently stuck inSTARTING
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 alternatelyRunning
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
The text was updated successfully, but these errors were encountered: