-
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
Unable to start with podman driver on rpi 4 - panic: runtime error: index out of range [1] with length 1 #12382
Comments
Looks like an issue with creating the private podman network, when running on arm64... Apparently the real error is not logged properly, and then we get an empty list of networks |
Looks like somehow minikube container is not getting created. Any pointers how to debug it further?
|
I get the same error for: OS: Ubuntu 21.04 5.11.0-31-generic x86_64 Full output:
The referenced issue does not really help: #8426 |
Thanks, its working now. |
Steps to reproduce the issue:
minikube --driver=podman start
Full output of
minikube logs
command:I0901 18:23:35.399582 44520 out.go:165]
I0901 18:23:35.401831 44520 out.go:165] ==> Last Start <==
I0901 18:23:35.404326 44520 out.go:165] Last start log file not found at /home/pi/.minikube/logs/lastStart.txt
I0901 18:23:35.406694 44520 out.go:165]
I0901 18:23:35.406783 44520 out.go:286] Setting OutFile to fd 1 ...
I0901 18:23:35.406812 44520 out.go:338] isatty.IsTerminal(1) = true
I0901 18:23:35.407047 44520 mustload.go:65] Loading cluster: minikube
I0901 18:23:35.409465 44520 cli_runner.go:115] Run: sudo -n podman container inspect minikube --format={{.State.Status}}
W0901 18:23:35.563843 44520 cli_runner.go:162] sudo -n podman container inspect minikube --format={{.State.Status}} returned with exit code 125
I0901 18:23:35.568694 44520 out.go:165]
W0901 18:23:35.569027 44520 out.go:230] ❌ Exiting due to GUEST_STATUS: state: unknown state "minikube": sudo -n podman container inspect minikube --format=: exit status 125
stdout:
stderr:
Error: error inspecting object: no such container minikube
W0901 18:23:35.569087 44520 out.go:230]
Full output of failed command:
goroutine 300 [running]:
k8s.io/minikube/pkg/drivers/kic/oci.podmanNetworkInspect(0x1a77125, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1fdab68, ...)
/app/pkg/drivers/kic/oci/network_create.go:242 +0x5c4
k8s.io/minikube/pkg/drivers/kic/oci.containerNetworkInspect(0x4001ba9110, 0x6, 0x1a77125, 0x6, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/app/pkg/drivers/kic/oci/network_create.go:161 +0x138
k8s.io/minikube/pkg/drivers/kic/oci.CreateNetwork(0x4001ba9110, 0x6, 0x4001ba90d8, 0x8, 0x2, 0x4022a0fce4, 0x6, 0x1be2c, 0x2e637e8)
/app/pkg/drivers/kic/oci/network_create.go:73 +0x108
k8s.io/minikube/pkg/drivers/kic.(*Driver).Create(0x4000f43e00, 0x18, 0x40001a2db0)
/app/pkg/drivers/kic/kic.go:95 +0x37c
k8s.io/minikube/pkg/minikube/machine.(*LocalClient).Create(0x4000572e80, 0x4000d213e0, 0x0, 0x0)
/app/pkg/minikube/machine/client.go:242 +0x418
k8s.io/minikube/pkg/minikube/machine.timedCreateHost.func2(0x2037598, 0x4000572e80, 0x4000d213e0, 0x4000f0e7c0, 0x4000c6cbd0)
/app/pkg/minikube/machine/start.go:193 +0x38
created by k8s.io/minikube/pkg/minikube/machine.timedCreateHost
/app/pkg/minikube/machine/start.go:192 +0xd4
System details:
OS: Debian GNU/Linux 11 (bullseye) ARM 64 bit
Podman version: 3.0.1
minikube version: v1.22.0
I checked existing issues but nothing helped.
The text was updated successfully, but these errors were encountered: