Minikube 挂载：错误的文件描述符

Question

When I mount a directory in Minikube and list out the directory, I get the errors below:

ls: cannot access '/mnt/nilla/assets': Bad file descriptor
ls: cannot access '/mnt/nilla/lib': Bad file descriptor
ls: cannot access '/mnt/nilla/priv': Bad file descriptor
ls: cannot access '/mnt/nilla/config': Bad file descriptor
ls: cannot access '/mnt/nilla/README.md': Bad file descriptor
ls: cannot access '/mnt/nilla/mix.exs': Bad file descriptor
ls: cannot access '/mnt/nilla/test': Bad file descriptor
ls: cannot access '/mnt/nilla/testmount': Bad file descriptor
total 0
-????????? ? ? ? ?            ? README.md
d????????? ? ? ? ?            ? assets
d????????? ? ? ? ?            ? config
d????????? ? ? ? ?            ? lib
-????????? ? ? ? ?            ? mix.exs
d????????? ? ? ? ?            ? priv
d????????? ? ? ? ?            ? test
-????????? ? ? ? ?            ? testmount

This is problem because when I mount this directory in my pod, the lsyncd service is copying it to a distribution folder. lsyncd does not know what to do with files that don't have proper descriptors.

I mount the the volume after starting Minikube, like:

nohup minikube mount ${HOME}/Development/nilla/:/mnt/nilla &> /dev/null &

How can I mount a directory and transfer the normal file descriptors that appear when I list the directory on my local computer? These are what they look like:

$ < ls -l nilla/
total 28
drwxr-xr-x 6 joes joes 4096 Apr 10 22:23 assets
drwxr-xr-x 2 joes joes 4096 Apr 10 22:23 config
drwxr-xr-x 4 joes joes 4096 Apr 10 22:23 lib
-rw-r--r-- 1 joes joes 1905 Apr 10 22:23 mix.exs
drwxr-xr-x 4 joes joes 4096 Apr 10 22:23 priv
-rw-r--r-- 1 joes joes  735 Apr 10 22:23 README.md
drwxr-xr-x 4 joes joes 4096 Apr 10 22:23 test
-rw-rw-r-- 1 joes joes    0 May 15 23:08 testmount

Additional notes: I'm using System 76's Pop OS, which is a fork of Ubuntu 20, and my Minikube VM is running Ubuntu 20 on Virtual Box.

Thanks.

Answer 1

@MikołajGłodziak in the comments pointed me in the right direction. The problem was the default driver for Minikube. I changed my minikube start command to specify one of the recommended drivers . As an example:

minikube start --driver=docker --mount-string ${HOME}/project/:/mnt/project

NOTE: You may get errors for trying to start up the same Minikube VM with a different driver. If that's the case, minikube delete will delete your current VM and make a new one the next time you run minikube start .

Answer 2

This seems to be an issue with minikube, which is currently being worked on.

See https://github.com/kubernetes/minikube/issues/12301

Current workaround is to use another driver .

Answer 3

easy way to do this

minikube start --driver=docker --mount-start="${HOME}/project/host" --mount