-
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 start fails with 'no such file or directory', reboot resolves issue on Mac M1 #16163
Comments
A friendly reminder that this issue had no activity for 30 days. |
@baude do you think this is a leak in gvisor or somewhere else? |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
+1 I have also been experiencing this issue. For me it seems to happen often after the laptop is restarted |
This issue should have been fixed by now. The start+stop sequences have been made much more robust in the meantime. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
We are seeing an issue on a self-hosted github runner, on Mac M1. If it's not already running, we start the podman machine at the start of the github job,
Usually this works, but at some point after a few days the machine gets into a state where it won't start. Rebooting fixes the issue, but it would be nice to identify a less drastic workaround.
Steps to reproduce the issue:
Sorry, this isn't super-reproducible since it only happens after a while. We see the issue when the machine has been running for a few days, but then stops (crashes?) and won't start correctly. I don't have logs for why it stops.
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
This is a Mac M1.
The text was updated successfully, but these errors were encountered: