Closed DNCoelho closed 4 years ago
Based on what you've shown, it looks like you want to just get it up and running. When I use Minikube, I just use the command
minikube start --vm-driver=virtualbox --memory=12000 --cpus=4 --kubernetes-version=v1.15.9
@Jimmyjim123 Thank you for the answer, however, I don't intend to get minikube working with a VM driver. What I want is to get it working with a docker driver in a VM. Sorry if I was not clear.
Strange that it says that The system verification failed.
, but then don't show any errors (only warnings) ?
I wonder about this one: --extra-config=kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
It seems related to the failed: open /run/systemd/resolve/resolv.conf: no such file or directory
Why was it added ?
@afbjorklund
Thank you for noticing that! That config was used in an old host to solve a problem relative to access to the host's network, or so it was explained to me. As this new VM was created with that host as a base I assumed that config was needed, but it does not seem to be the case. The cluster seems to start correctly without it so I'll close the issue for now. If I do confirm that some problem persists I'll reopen it.
Thank you very much for your help!
Steps to reproduce the issue:
minikube start --driver=docker --extra-config=kubelet.resolv-conf=/run/systemd/resolve/resolv.conf --alsologtostderr -v=1
Full output of failed command:
Full output of
minikube start
command used, if not already included:Optional: Full output of
minikube logs
command:Any help would be greatly appreciated!