minikube with podman on macOS darwin/amd64 doesn't work #12658
Comments
afbjorklund
added
co/podman-driver
|
Ok, thanks. Tried building from source and received "error storing credentials in temporary auth file": Same result without CRI-O. |
|
Full log with
|
|
Podman stumbles on some Docker config, so you need to move that aside... You might want to try some simpler containers first, before trying kicbase
|
|
Thanks. Now I'm hitting podman run returns error "unexpected end of JSON input" so I'll wait for that fix to roll out. |
|
Solved the "unexpected end of JSON input" issue with the latest CoreOS so I can now run
|
|
Did you run the "root" Podman ? |
|
You're right, I was not using "root" podman. After switching, now there's an error
|
|
There needs to be a warning for that, similar to the one for docker. Just that running podman-remote is quite new. Eventually, minikube and kubernetes will support rootless containers as well. But until it works, it should warn... |
|
Seems to be the volume (and possibly the network) from a previous run that are "in the way" ? Maybe remove manually.
|
I did a It seems to me the volume error is because it tries again after failing the first time. The first error seems to be this though I'm not sure if it's benign: Then it seems the next major error is: |
|
Hi, I started with minikube and ran into the same issue and switched to kind. Though I ran there into the same issue but I was able to troubleshoot it. I guess this could help here as well: kubernetes-sigs/kind#2445 (comment) hth |
|
I also encountered the same issue, and stderr output below: tcpproxy: for incoming conn 127.0.0.1:64275, error dialing "192.168.127.2:33131": connect tcp 192.168.127.2:33131: connection was refused
|
|
Port mapping bind 127.0.0.1, but vm of podman refuse connection from host to connect 127.0.0.1. I find an issue in podman project: containers/podman#11528 After change ❌ Exiting due to GUEST_START: Failed to setup kubeconfig: RoutableHostIPFromInside is currently only implemented for linux |
Where do you change this? |
|
@kgibm See this line minikube/pkg/drivers/kic/oci/oci.go Line 509 in 3232254 I change it to publish := fmt.Sprintf("--publish=%d", pm.ContainerPort) |
Yes. Is this a bug? Should the Also, I see the same error, "Unable to get host IP: RoutableHostIPFromInside is currently only implemented for linux" although it doesn't seem to be fatal. Steps: |
|
Also, stopping resulted in errors: |
|
Thank @kgibm, I can confirm that, with that change I`ve been able to run minikube on Arm based Mac. |
|
I get the same error |
|
I also have the same error but @kgibm change didn't help to resolve it. |
|
Hi everyone, I'm getting the same ssh error. I'll try with building minikube myself with that line change suggested hopefully some point this week. Any more progress on this issue to know about? |
|
I had the same issue, suggestion from @kgibm works like charm. During multiple rebuild it is clear that important step not to miss is |
This is being addressed: If you want to run as rootless. |
|
I had the issue even running as root. It was only resolved after the patch: |
|
can confirm the patch is necessary to make it work. patched and build the current stable. v1.25.1. with this minikube startup works fine. hope to see this fixed in a new release in the future :) |
spowelljr
added
the
long-term-support
|
Just coming up to speed on this thread. @spowelljr does the tag you added mean we're SOL if in this boat? |
|
Hi @dwelch2344, it was just added because it's a support issue that's been up for more than 6 months. I can easily change the line @kgibm suggested, I would only do it for macOS specifically as I don't want to change the behavior on Linux unless we can be sure that it works on Linux as well. Anyone else is free to make the PR themselves if that interested them, but making this change in general shouldn't be an issue. |
|
Yeah, definitely makes sense to do it only for Mac. -le sigh- Haven't pulled the project to try this myself as I found another solution for my current needs, but def would love to see this fixed for the future as I'm pitching a dev practice (including minikube) to an org right now. Will take a look through the codebase asap. Is there a good example for handling platform specific scenarios like this someone could point me to? If not, I'll jungle around – just figure might someone might have a shortcut handy :D |
|
For something small like this, minikube/cmd/minikube/cmd/start.go Line 1043 in 5fb961c |
Signed-off-by: Kevin Grigorenko <kevin.grigorenko@us.ibm.com>
|
Created PR #14290 |
Steps to reproduce the issue:
brew:podman machine:Run
minikube logs --file=logs.txtand drag and drop the log file into this issueIf this is a known issue, maybe it should be added to the "Known Issues" section?
Full output of failed command if not
minikube start:The text was updated successfully, but these errors were encountered: