-
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
Minikube with Podman on Mac: "no such container "minikube" #13261
Comments
The error reporting of that command is truly awful...
But it looks like the underlying issue is cgroup-related ?
|
Unfortunately it is not possible to troubleshoot on the developer machines at the moment, hard-coded on the We might want to enable running |
Same error on Linux:
The main issue seems to be that podman machine runs as rootless by default, which minikube doesn't support yet. To fix:
|
There are other things left to fix, before Podman Machine (i.e. running |
it does not work for me. ➜ ~ podman version Server: ➜ ~ minikube version OS: macOS 11.4 M1 |
Same issue, the solution mentioned does not work. It seems that a connection attempt is made to a port (36225 in this case) and whatever is listening there closes the connection:
This is on a M1 Pro macbook. minikube_logs_5e2f0f0e127cd776a9181abdfefb7fb9b0a78ebb_0.log Tried to run on the local IP my MacBook uses: This opened a new set of errors that I think is a new issue worth. |
Hi @tbrodbeck, did you have a chance to review the above comments by @afbjorklund? |
Sorry, I stopped using podman and switched back to Docker. Therefore, I cannot reproduce it anymore. |
Hi @tbrodbeck – thanks for your response, will close out this issue for now. Please feel free to re-open the issue by commenting with Thank you for sharing your experience! |
@klaases There are multiple users reporting this issue, why close it? |
Same issue 😞 |
❌ Exiting due to GUEST_STATUS: state: unknown state "minikube": podman container inspect minikube --format=: exit status 125 stderr: ❯ podman version Server: ❯ minikube version |
Podman on Mac is still experimental, but we will continue to look in to it. |
/reopen |
@afbjorklund: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Seems to be same root cause as #13618, but there were not enough logs from this restart. 🔄 Restarting existing podman container for "minikube" ... Follow up in the other issue. |
did manage to fix this after trying |
minikube start --nodes=4 stderr: 🔄 Restarting existing podman container for "minikube" ... stderr: ❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: driver start: start: podman start minikube: exit status 125 stderr: ╭───────────────────────────────────────────────────────────────────────────────────────────╮ I am getting this, can anyone help me to sort this out MacOS |
For anyone who may be coming here that is experiencing this issue on an M series Mac and podman. Running the following may clear up the issue with
|
not working.
|
FWIW I setup podman with |
What Happened?
I cannot start minikube sucessfully with Podman:
Attach the log file
minikube_logs_b5071b5f0b4713dd674799360d6dd0b30509408b_0.log
Operating System
macOS (Default)
Driver
Podman
The text was updated successfully, but these errors were encountered: