docker fails if --docker-opt storage-driver=overlay2 is set

[fredsted]

Started having this problem after upgrading to 1.8.2.

It disappeared after downgrading to back to 1.7.x. Could not find anything recent regarding this anywhere else.

I've tried deleting the ~/.minikube folder and reinstalling minikube via homebrew. Didn't help.

Example of output (see link to full logs below)

W0317 10:02:52.019784    1773 exit.go:101] Unable to start VM. Please investigate and run 'minikube delete' if possible: creating host: create: Error creating machine: Error running provisioning: ssh command error:
command : sudo systemctl -f restart docker
err     : Process exited with status 1
output  : Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

The exact command to reproduce the issue:

minikube start --v 10 --logtostderr \
  --disk-size="20G" \
  --cpus="4" \
  --docker-opt storage-driver=overlay2 \
  --extra-config=apiserver.authorization-mode="RBAC" \
  --kubernetes-version v1.15.5 \
  --memory="5120" \
  --network-plugin=cni \
  --enable-default-cni \
  --vm-driver="hyperkit"

The full output of the command that failed:

See here: https://sf.gl/files/minikube-out.txt

The operating system version:
macOS 10.15.3

[tstromberg]

Interesting! Can you share the output of:

• minikube logs
• minikube ssh "systemctl status docker.service"

Thanks!

Also, can you check if removing this flag fixes your issue:

• --docker-opt storage-driver=overlay2

[fredsted]

Thanks for the quick response.

Removing the --docker-opt storage-driver=overlay2 flag solved the issue!

Here's the minikube logs output: https://sf.gl/files/minikube-logs-output.txt – unfortunately couldn't get more since the VM isn't starting.

Looks like since the storage driver configuration property is duplicated, it errors out?

[tstromberg]

@fredsted - Indeed, it seems this is the case:

Mar 19 07:38:09 minikube dockerd[2034]: unable to configure the Docker daemon with file /etc/docker/daemon.json: the following directives are specified both as a flag and in the configuration file: storage-driver: (from flag: overlay2, from file: overlay2)

I believe that this happened in v1.8.x because minikube now needs overlay2 for the image preload optimizations.

It looks like we could do something smarter about this.