-
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 on podman driver: failed to start node: RoutableHostIPFromInside #7951
Comments
this is a bug, that could be related to @tstromberg PR |
Not sure what the fix is, for Docker we use the local bridge:
Presumably something similar, to get the podman CNI bridge ?
Not sure how to inspect it, though. Poke around in {
"cniVersion": "0.4.0",
"name": "podman",
"plugins": [
{
"type": "bridge",
"bridge": "cni-podman0",
"isGateway": true,
"ipMasq": true,
"ipam": {
"type": "host-local",
"routes": [{ "dst": "0.0.0.0/0" }],
"ranges": [
[
{
"subnet": "10.88.0.0/16",
"gateway": "10.88.0.1"
}
]
]
}
}
]
} Or just look at the
Could probably do that for docker as well as for podman:
|
We can access the container's gateway via the following command:
Thing is: do we have the container's ID or name? |
We do. // RoutableHostIPFromInside returns the ip/dns of the host that container lives on
func RoutableHostIPFromInside(ociBin string, containerName string) (net.IP, error) |
Left the docker hacks in place. Not sure what do for podman-remote, lookup the host name ? |
OS: Fedora 31 (64 bit)
podman: 1.9.0
minikube: 1.10.0-beta.2
Error description: when I try to start minikube with podman driver, it fails with the following message:
I'm not quite sure if that bug is relevant (no mention of RoutableHostIPFromInside).
Steps to reproduce the issue:
minikube start --driver=podman
Full output of failed command:
Thank you very much.
The text was updated successfully, but these errors were encountered: