Skip to content
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

Fix "Failed to stop docker.service: Unit docker.service not loaded" log error on start with kvm2 driver and containerd/crio runtimes #11622

Closed
ilya-zuyev opened this issue Jun 10, 2021 · 1 comment · Fixed by #11667
Labels
co/kvm2-driver KVM2 driver related issues co/runtime/containerd kind/regression Categorizes issue or PR as related to a regression from a prior release. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@ilya-zuyev
Copy link
Contributor

ilya-zuyev commented Jun 10, 2021

when minikube is starting we try to disable non-active runtimes , but for kvm2/containerd combination it leads to a log error
E0610 10:36:19.140582 12060 docker.go:159] "Failed to stop" err="sudo systemctl stop -f docker.service: Process exited with status 5\nstdout:\n\nstderr:\nFailed to stop docker.service: Unit docker.service not loaded.\n" service="docker.service"

ilyaz@skeletron --- g/minikube ‹master* ?› » out/minikube start --driver=kvm2 --container-runtime=containerd                                                                                                                                         7 ↵
* minikube v1.21.0-beta.0 on Ubuntu 21.04
* Using the kvm2 driver based on existing profile
* Starting control plane node minikube in cluster minikube
* Restarting existing kvm2 VM for "minikube" ...
E0610 10:36:19.140582   12060 docker.go:159] "Failed to stop" err="sudo systemctl stop -f docker.service: Process exited with status 5\nstdout:\n\nstderr:\nFailed to stop docker.service: Unit docker.service not loaded.\n" service="docker.service"
* Preparing Kubernetes v1.20.7 on containerd 1.4.4 ..
* ```
@afbjorklund
Copy link
Collaborator

Docker was normally always started, due to using Docker Machine.

@spowelljr spowelljr added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 15, 2021
@spowelljr spowelljr added this to the 1.23.0-candidate milestone Jun 15, 2021
@spowelljr spowelljr added the kind/regression Categorizes issue or PR as related to a regression from a prior release. label Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/kvm2-driver KVM2 driver related issues co/runtime/containerd kind/regression Categorizes issue or PR as related to a regression from a prior release. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
3 participants