-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
unsupported graph driver: btrfs #6167
Comments
All I could find so far is a hint to use edit: ...and kubernetes v1.17.0 is the first version that fails with this error. I just checked v1.16.4 and it works fine. |
Sounds like an upstream (kubeadm) issue, apparently btrfs is not supported |
These are the currently supported Docker configurations: (not sure when it changed) RuntimeSpec: RuntimeSpec{
DockerSpec: &DockerSpec{
Version: []string{`1\.1[1-3]\..*`, `17\.0[3,6,9]\..*`, `18\.0[6,9]\..*`, `19\.03\..*`},
GraphDriver: []string{"aufs", "overlay", "overlay2", "devicemapper", "zfs"},
},
}, https://github.com/kubernetes/system-validators/blob/v1.0.4/validators/types_unix.go#L63 |
From what I can tell, we only skipped the check for Kubernetes < 1.13 (not 1.16) |
I just ran into this issue on Arch Linux with minikube v1.6.2. I can provide details if you like. |
Can you open an issue with upstream, if indeed kubernetes is working fine with the btrfs driver ? This is really something with kubeadm, and not with minikube (since we are using overlay2 in VM) If you want to use it anyway, you can use the mentioned ignore-preflight-errors option to kubeadm:
|
For this issue, I think the updates to the documentation we need are:
The documentation should live on this page: If anyone is interested in taking this issue, please comment here and I can assign the issue to you. I'm happy to review any PRs. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
This feels like a kubeadm issue, if it indeed isn't and needs work in minikube, please reopen this. |
The exact command to reproduce the issue:
$ sudo minikube start --vm-driver=none
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version:
Arch Linux with kernel 5.4.6
The text was updated successfully, but these errors were encountered: