search

kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
29.15k stars 4.86k forks source link

Minikube VirtualBox Win 10 amd-64 1.33.1 Failed to start Docker Application Container Engine #19035

Open jsbiff opened 3 months ago

jsbiff commented 3 months ago

What Happened?

When I try to create a new VM, using the Virtualbox driver, on Windows 10 amd-64, currently the default image it downloads and starts is v1.33.1. This image, upon boot up, fails to start Docker (see attached logs).

If I delete the VM and create a new one, forcing it to use 1.33.0 iso, it starts up fine with no errors. The problem seems to be specific to iso version 1.33.1

Attach the log file

minikube_logs.txt.gz

Operating System

Windows

Driver

VirtualBox

jsbiff commented 3 months ago

Update: Have reproduced the issue on a different system, running Win 11, with the hyper-v driver. Definitely a problem with the current image, and not driver specific as it turns out.

JiangJungle commented 3 months ago

I encountered the same problem, Docker failed to start. Have you solved this problem?

Jun 10 13:31:04 minikube systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Jun 10 13:31:04 minikube systemd[1]: docker.service: Failed with result 'exit-code'. Jun 10 13:31:04 minikube systemd[1]: Failed to start Docker Application Container Engine. Jun 10 13:31:04 minikube systemd[1]: docker.service: Scheduled restart job, restart counter is at 11. Jun 10 13:31:04 minikube systemd[1]: Stopped Docker Application Container Engine. Jun 10 13:31:04 minikube systemd[1]: Starting Docker Application Container Engine... Jun 10 13:31:04 minikube dockerd[1499]: time="2024-06-10T13:31:04.690425791Z" level=info msg="Starting up" Jun 10 13:32:04 minikube dockerd[1499]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": failed to dial "/run/containerd/containerd.sock": context deadline exceeded Jun 10 13:32:04 minikube systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE Jun 10 13:32:04 minikube systemd[1]: docker.service: Failed with result 'exit-code'. Jun 10 13:32:04 minikube systemd[1]: Failed to start Docker Application Container Engine. Jun 10 13:32:04 minikube systemd[1]: docker.service: Scheduled restart job, restart counter is at 12. Jun 10 13:32:04 minikube systemd[1]: Stopped Docker Application Container Engine. Jun 10 13:32:04 minikube systemd[1]: Starting Docker Application Container Engine... Jun 10 13:32:04 minikube dockerd[1524]: time="2024-06-10T13:32:04.940157812Z" level=info msg="Starting up" Jun 10 13:33:04 minikube dockerd[1524]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": failed to dial "/run/containerd/containerd.sock": context deadline exceeded

jsbiff commented 2 months ago

@JiangJungle I was able to force minikube to create a new vbox vm using the image for the previous version, by deleting the existing vm with:

Then, forced it to create a VM using the previous image version (NOTE: It appears to me that today this is no longer necessary because minikube start with no args is downloading the prior version anyhow - although perhaps it's just re-using my last selection, I'm not sure; but it may be that the minikube devs removed the broken image from the repositories so that minikube falls back to the most recent available version):