Open cbr7 opened 2 months ago
should it be more reported on podman side ? Podman Desktop is not involved if basically it's just 'podman start', 'run a container' and call 'podman machine stop'
Reproduced on Mac OS 14 M2.
But it eventually stopped. Even with an error, but stopped.
Created issue https://github.com/containers/podman/issues/22515 in podman repo.
@cbr7 thanks!
I've checked with podman 4.9.4 and it's still 1mn
There is area for improvement but it looks it's not a 'new issue' (for the severity)
If you try with containers without interactive shell it should be immediate
While trying to reproduce this issue and I was able to stop the machine with no problems, but it wouldn't start again, ending the process with "Command execution failed with exit code 125" as well.
@cbr7 We have patch merged in upstream, we could test it out, although, I am not sure where it should land exactly (client, engine inside vm?)
Bug description
It seems that on macOS(wasn't able to reproduce on windows 11) it's not possible to stop a podman machine after starting a container, however after the fail error is throw all the images/containers/pods will become unavailable, presumably because the podman machine entering some error state.
https://github.com/containers/podman-desktop/assets/106525396/5feeba0d-375a-49fd-8bc5-fe5782158e70
Operating system
macOS
Installation Method
Installer from website/GitHub releases
Version
1.10.0
Steps to reproduce
Relevant log output
Additional context
No response