Can't start minikube with docker driver on zfs

[R-M-F-at-C-A]

What Happened?

Similar to (unresolved) issue #10929

Running
minikube start (or minikube start --driver=docker) gives

😄  minikube v1.29.0 on Ubuntu 22.04
    ▪ KUBECONFIG=[redacted]
✨  Using the docker driver based on user configuration
❗  docker is currently using the zfs storage driver, consider switching to overlay2 for better performance
📌  Using Docker driver with root privileges
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
🔥  Creating docker container (CPUs=2, Memory=11900MB) ...

❌  Exiting due to RUNTIME_ENABLE: sudo systemctl restart 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.

Log.txt attached.

I've tried the suggestions at #10929:

docker system prune
minikube delete
minikube start --driver=docker

and

sudo systemctl unmask docker
sudo systemctl start docker

Attach the log file

logs.txt

Operating System

Ubuntu

Driver

Docker

[farnsworth]

Same problem here. Did you find any solution?
Only way I found to fix was to downgrade minikube to v1.27.0.

[JohSchillerEmnify]

Running into the same issue. I will try downgrading but in the long term there should be some solution to this. My logs look similar to yours. same errors with overlayfs

Update: downgraded to 1.27.1 and can confirm it is working.

[Ed-Commodum]

I'm having the same issue, downgrading to 1.27.0 fixed the problem.

[software-engr-full-stack]

This may be related to the usage of docker and zfs as the underlying FS. It seems minikube doesn't work if docker is using zfs as the storage driver. You have to make docker use the overlay2 storage driver. To do that, see this https://blog.chlc.cc/p/docker-and-zfs-a-tough-pair/.

Basically: 1) stop the docker service, 2) create a zfs volume, 3) format that volume (btrfs type seems to work, if you're having issues, use ext4), 4) mount the zfs volume to /var/lib/docker or wherever your docker data is located, 5) start the docker service.

I was able to make this work with the latest version which is v1.31.0 at the time of this writing.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.