-
Notifications
You must be signed in to change notification settings - Fork 5k
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 start
with podman
driver fails with index ouf range
error
#12489
Comments
Thank you for sharing your experience! Also please attach (drag) the
/triage needs-information |
|
@oliversalzburg thats odd I dont see that error in the file you attached, I am curious would this help if you purge minikube?
|
in the Audit there is no minikube start, I am curious do u Ctrl+C the minikube start or is it just hangning ?
|
I didn't Ctrl+C any of the processes I was running yesterday. I just went through several iterations of start+delete to see if I can find my mistake. I now ran I then ran |
@medyagh Any idea what else I should be looking into? |
hm... I dont know why your system doesnt not make a full log, your log file seems missing a lot of information @spowelljr any idea why the log is not complete ? |
For completeness, I also ran the commands again, after upgrading everything to the latest versions. Here are the logs and output: oliver@oliver-work:~$ minikube start --driver=podman --container-runtime=cri-o
😄 minikube v1.23.2 on Debian 11.1
✨ Using the podman driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
💾 Downloading Kubernetes v1.22.2 preload ...
> preloaded-images-k8s-v13-v1...: 579.76 MiB / 579.76 MiB 100.00% 62.52 Mi
> gcr.io/k8s-minikube/kicbase: 355.39 MiB / 355.40 MiB 100.00% 16.34 MiB p
E1021 10:26:42.945679 3849 cache.go:201] Error downloading kic artifacts: not yet implemented, see issue #8426
🔥 Creating podman container (CPUs=2, Memory=12800MB) ...- panic: runtime error: index out of range [1] with length 1
goroutine 335 [running]:
k8s.io/minikube/pkg/drivers/kic/oci.podmanNetworkInspect({0x1eb9aed, 0x6})
/app/pkg/drivers/kic/oci/network_create.go:242 +0x7f0
k8s.io/minikube/pkg/drivers/kic/oci.containerNetworkInspect({0xc025ee8320, 0xc0005d5a80}, {0x1eb9aed, 0xb})
/app/pkg/drivers/kic/oci/network_create.go:161 +0x19e
k8s.io/minikube/pkg/drivers/kic/oci.CreateNetwork({0xc025ee8320, 0x6}, {0xc025ee82e8, 0x1eb4d98})
/app/pkg/drivers/kic/oci/network_create.go:73 +0x1ed
k8s.io/minikube/pkg/drivers/kic.(*Driver).Create(0xc000d51e00)
/app/pkg/drivers/kic/kic.go:95 +0x496
k8s.io/minikube/pkg/minikube/machine.(*LocalClient).Create(0xc001437fc0, 0xc001480ea0)
/app/pkg/minikube/machine/client.go:242 +0x5f2
k8s.io/minikube/pkg/minikube/machine.timedCreateHost.func2()
/app/pkg/minikube/machine/start.go:193 +0x38
created by k8s.io/minikube/pkg/minikube/machine.timedCreateHost
/app/pkg/minikube/machine/start.go:192 +0x17d
oliver@oliver-work:~$ minikube logs --file=logs.txt
❌ 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
╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 If the above advice does not help, please let us know: │
│ 👉 https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ Please also attach the following file to the GitHub issue: │
│ - /tmp/minikube_logs_a15606cd8c429498f482f0869e7ab4a2ed08e63b_0.log │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────╯ logs.txt |
Thanks for the logs @oliversalzburg, I've found the bug and will push up a PR soon. |
@spowelljr Is #12382 maybe the same as this one? |
@oliversalzburg Yup, thanks for pointing it out I commented on it |
Steps to reproduce the issue:
minikube start --driver=podman --container-runtime=cri-o
I'm running this in a WSL2 environment with Debian 11 Bullseye.
I found #10088 and #10110, which seemed to relate to the same issue, but it seems like this should no longer be a problem with the version I'm using.
I see the
Error downloading kic artifacts: not yet implemented
error, but also couldn't make sense of either the referenced issue #8426 or other tickets mentioning this error.logs.txt
Full output of failed command if not
minikube start
:The text was updated successfully, but these errors were encountered: