none without Docker installed: sudo systemctl start docker: exit status 5

[laith-leo]

Unable to start minikube in RHEL 8 based, due to the missing container runtime as a systemd service.

**[l@minikube ~]$ sudo minikube start --vm-driver=none
😄 minikube v1.4.0 on Centos 8.0.1905
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
🔄 Starting existing none VM for "minikube" ...
⌛ Waiting for the host to be provisioned ...

💣 Failed to enable container runtime: running command: sudo systemctl start docker: exit status 5

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose
[l@minikube ~]$ sudo minikube start --vm-driver=none --container-runtime=cri-o
😄 minikube v1.4.0 on Centos 8.0.1905
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
🔄 Starting existing none VM for "minikube" ...
⌛ Waiting for the host to be provisioned ...

💣 Failed to enable container runtime: running command: sudo systemctl restart crio: exit status 5

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose**:

CentOS Linux release 8.0.1905 (Core):

[afbjorklund]

Which runtime did you install/want, and what was the entire output of that system to start command ?

[afbjorklund]

It seems to install OK, as long as docker has been started and selinux has been disabled.

sudo yum install --nobest docker-ce
sudo setenforce 0

There doesn't seem to be any Docker version for CentOS 8 yet, so it installs an older version:

• docker-ce-18.06.3.ce-3.el7.x86_64

$ sudo minikube start --vm-driver=none
😄  minikube v1.4.0 on Centos 8.0.1905
🤹  Running on localhost (CPUs=2, Memory=3780MB, Disk=17394MB) ...
ℹ️   OS release is CentOS Linux 8 (Core)
🐳  Preparing Kubernetes v1.16.0 on Docker 18.06.3-ce ...
🚜  Pulling images ...
🚀  Launching Kubernetes ... 
🤹  Configuring local host environment ...

⚠️  The 'none' driver provides limited isolation and may reduce system security and reliability.
⚠️  For more information, see:
👉  https://minikube.sigs.k8s.io/docs/reference/drivers/none/

⚠️  kubectl and minikube configuration will be stored in /root
⚠️  To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:

    ▪ sudo mv /root/.kube /root/.minikube $HOME
    ▪ sudo chown -R $USER $HOME/.kube $HOME/.minikube

💡  This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=true
⌛  Waiting for: apiserver proxy etcd scheduler controller dns
🏄  Done! kubectl is now configured to use "minikube"
💡  For best results, install kubectl: https://kubernetes.io/docs/tasks/tools/install-kubectl/

The console looks rather poor, though:

[laith-leo]

You are correct, but I don't want to use Docker, I'm using RHEL8 and want to use Podman for containers management .

[afbjorklund]

It seems that the messages above ("exit status 5") are a symptom of the software not being installed:

Failed to start crio.service: Unit crio.service not found.

[afbjorklund]

You are correct, but I don't want to use Docker, I'm using RHEL8 and want to use Podman for containers management .

It seems that there is no crio package for CentOS 8 yet, and for RHEL you are supposed to use OpenShift (rather than Kubernetes)... Podman can run containers, but for this you will need CRI-O.

[afbjorklund]

Regular podman run is having some out-of-the-box issues as well:
error configuring network namespace for container 8cf402b2d46c31e7fc80fa3a215342b510e18ebc3510e8baf92df941cad4bbd0: Missing CNI default network

Possibly it could be the old version used (1.0.2). But /etc/cni/net.d is empty ?
Could try the "container-tools" module, but I think this will do (podman load)

[laith-leo]

@afbjorklund RHEL8 uses[1] runc as a Container runtime instead of Docker, and this is the argument I wanted to pass in the --container-runtime but it didn't work, minikube needs the container-runtime as a daemon while it is not a daemon in RHEL8 anymore.

[1] 1.3 in https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index

[laith-leo]

@afbjorklund
The CNI default is there, here is the contents of /etc/cni/net.d/87-podman-bridge.conflist:

root@centos8 net.d]# cat 87-podman-bridge.conflist

{
    "cniVersion": "0.3.0",
    "name": "podman",
    "plugins": [
      {
        "type": "bridge",
        "bridge": "cni0",
        "isGateway": true,
        "ipMasq": true,
        "ipam": {
            "type": "host-local",
            "subnet": "10.88.0.0/16",
            "routes": [
                { "dst": "0.0.0.0/0" }
            ]
        }
      },
      {
        "type": "portmap",
        "capabilities": {
          "portMappings": true
        }
      }
    ]
}

[afbjorklund]

RHEL8 uses[1] runc as a Container runtime instead of Docker,

Docker also uses runc, so those are different types of runtimes...

[afbjorklund]

We should give a better error message, when trying to use the none driver without having the runtime installed (and running). Currently the output is cryptic, and surely doesn't offer any help remedying:

💣 Failed to enable container runtime: running command: sudo systemctl start docker: exit status 5

It should say something happy like "you need to install a container runtime" (docker/containerd/cri-o)

[laith-leo]

@afbjorklund
Well the problem is that there is a container runtime already installed in the RHEL8/CentOS8, but the problem is that minikube can't see it, because minikube sees the container runtime only if it is a service/daemon, while it is in the RHEL8/CentOS8 is an embedded with systemd (serverless style).

[afbjorklund]

@laith-leo : maybe this helps to explain: https://www.ianlewis.org/en/tag/container-runtime-series

[afbjorklund]

The CNI default is there, here is the contents of /etc/cni/net.d/87-podman-bridge.conflist

Yes, it was included with the podman package. No idea why the file when missing, first time.