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

Exiting due to RUNTIME_ENABLE on minikube start #12421

Closed
bouteillerAlan opened this issue Sep 7, 2021 · 2 comments
Closed

Exiting due to RUNTIME_ENABLE on minikube start #12421

bouteillerAlan opened this issue Sep 7, 2021 · 2 comments
Labels
co/docker-driver Issues related to kubernetes in container kind/support Categorizes issue or PR as a support question. os/linux triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@bouteillerAlan
Copy link

Steps to reproduce the issue:

  1. install docker & docker compose on fedora (i have a podman instance too)
  2. set up docker to run without sudo
  3. install kubectl
  4. install stable minikube via rpm in linux x86/64 via the website instruction
  5. run minikube start --driver=docker

result of minikube start

😄  minikube v1.23.0 on Fedora 34
✨  Using the docker driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
🏃  Updating the running docker "minikube" container ...

❌  Exiting due to RUNTIME_ENABLE: sudo systemctl start docker: Process exited with status 1
stdout:

stderr:
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.


╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  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.    │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

minikube logs --file=logs.txt give
logs.txt

systemctl status docker.service give

● docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
     Active: active (running) since Tue 2021-09-07 18:29:08 CEST; 23min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 822734 (dockerd)
      Tasks: 49
     Memory: 55.8M
        CPU: 1.788s
     CGroup: /system.slice/docker.service
             ├─822734 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
             ├─823132 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 49153 -container-ip 192.168.49.2 -container-port 32443
             ├─823145 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 49154 -container-ip 192.168.49.2 -container-port 8443
             ├─823158 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 49155 -container-ip 192.168.49.2 -container-port 5000
             ├─823170 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 49156 -container-ip 192.168.49.2 -container-port 2376
             └─823182 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 49157 -container-ip 192.168.49.2 -container-port 22

Sep 07 18:29:08 fedora dockerd[822734]: time="2021-09-07T18:29:08.339935838+02:00" level=info msg="Firewalld: interface docker0 already part of docker zone, returnin>
Sep 07 18:29:08 fedora dockerd[822734]: time="2021-09-07T18:29:08.449720463+02:00" level=info msg="Loading containers: done."
Sep 07 18:29:08 fedora dockerd[822734]: time="2021-09-07T18:29:08.488812426+02:00" level=info msg="Docker daemon" commit=75249d8 graphdriver(s)=overlay2 version=20.1>
Sep 07 18:29:08 fedora dockerd[822734]: time="2021-09-07T18:29:08.489414742+02:00" level=info msg="Daemon has completed initialization"
Sep 07 18:29:08 fedora systemd[1]: Started Docker Application Container Engine.
Sep 07 18:29:08 fedora dockerd[822734]: time="2021-09-07T18:29:08.514369379+02:00" level=info msg="API listen on /run/docker.sock"
Sep 07 18:29:12 fedora dockerd[822734]: time="2021-09-07T18:29:12.436918667+02:00" level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using de>
Sep 07 18:29:12 fedora dockerd[822734]: time="2021-09-07T18:29:12.437049217+02:00" level=info msg="IPv6 enabled; Adding default IPv6 external servers: [nameserver 20>
Sep 07 18:29:12 fedora dockerd[822734]: time="2021-09-07T18:29:12.632030596+02:00" level=warning msg="path in container /dev/fuse already exists in privileged mode" >
Sep 07 18:29:12 fedora dockerd[823242]: time="2021-09-07T18:29:12+02:00" level=info msg="Firewalld: docker zone already exists, returning"
lines 1-27/27 (END)

@afbjorklund
Copy link
Collaborator

afbjorklund commented Sep 7, 2021

This is due to btrfs, see other issues on the same topic: #7923

Sep 07 16:32:22 minikube dockerd[673]: failed to start daemon: error initializing graphdriver: /var/lib/docker contains several valid graphdrivers: btrfs, overlay2; Please cleanup or explicitly choose storage driver (-s <DRIVER>)

@afbjorklund afbjorklund added co/docker-driver Issues related to kubernetes in container os/linux labels Sep 7, 2021
@sharifelgamal sharifelgamal added triage/duplicate Indicates an issue is a duplicate of other open issue. kind/support Categorizes issue or PR as a support question. labels Sep 29, 2021
@sharifelgamal
Copy link
Collaborator

I'm going to go ahead and close this as a dupe of the known btrfs issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/docker-driver Issues related to kubernetes in container kind/support Categorizes issue or PR as a support question. os/linux triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

3 participants