-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
GH action does not support Start Stop #8052
Comments
This looks like the exact same issue that we were seeing with podman in #8033 The real error isn't actually the re-attaching to the old cgroups (since those are gone). The problem is about failing to create some fiiles, possibly due to read-only |
These lines are supposed to be enough:
And there doesn't seem to be any errors ? That should make But here it is still failing, the second time ?
For podman the issue was just that KIND only did the workaround for "docker", not "libpod_parent" |
For debugging this, you can get the ID of the minikube container and then look at the mount:
It supposed to be mounted as cgroup Seems like |
Doesn't seem to reproduce locally, can stop/start docker containers multiple times So it must be something specific to Azure Linux, or maybe just a fluke perhaps... |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
this happens only in github actions when trying to start a stopped kic. as seen in this PR: https://github.com/kubernetes/minikube/pull/8025/checks?check_run_id=658120043
The text was updated successfully, but these errors were encountered: