-
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
Minikube fails to start with docker driver on Ubuntu 18.04, Error: find: '/var/lib/dpkg': No such file or directory #11235
Comments
Something is wrong here (possibly btrfs), the
When that volume was prepared, it should have copied
|
Here is a test case:
It is supposed to use the "local" volume driver. $ sudo ls /var/lib/docker/volumes/test/_data
backups cache lib local lock log mail opt run spool tmp
$ sudo ls /var/lib/docker/volumes/test/_data/lib/dpkg
alternatives cmethopt diversions-old lock parts statoverride-old status-old updates
available diversions info lock-frontend statoverride status triggers |
See also #7923 |
@DoHuber does this comment help ? |
@medyagh @afbjorklund Thanks for the fast responses - I tried the docker test case and the command outputs look the same, and the "local" driver is in use. I'm currently in the process of switching away from btrfs as described in #7923, but this is taking some time due to a complex server setup. |
I have a mixed update of sorts: due to massive problems with switching docker to btrfs on the aforementioned complex setup, we've decided to ditch that machine completely and are now working on another with a much more straightforward one. There, using overlay2 is no problem and the problem has disappeared, everything is working as it should, so the facts seem to be pointing in the direction of this indeed being related to btrfs somehow. |
Hi, I'm confused, I have the exact same problem but the advice message says instead:
I don't see a workaround here, unless that's switching to overlay2 which is not an option for me... |
Steps to reproduce the issue:
minikube start --memory=20g --cpus=12 --driver=docker
I have tried the various fixes proposed in the error log, and also in #10302, but the issue still appears.
Full output of failed command:
Full output of
minikube start
command used, if not already included:See above
Optional: Full output of
minikube logs
command:To start a cluster, run: "minikube start"
The text was updated successfully, but these errors were encountered: