-
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 start --mount creates empty directory #4440
Comments
In my case, nothing is created at all. Does work using the MacOS, hyperkit, minikube v1.1.0 |
For my part, I get the same issue using |
When work starts on this, my feature request would be that mounts would become something you can manage ( |
I can't tell what vm-driver the OP is using, but in my case the problem is with hyperkit. |
The good news here is that mount implementation is driver independent. The bad news is that the underlying server used isn't so great. Any chance this directory has many (>600) files? |
In my case it's PHP projects with composer packages. So 600 is something that is easy to reach (current subproject has 6000+ already, including cache files etc: |
This issue appears to be a duplicate of #2481, so I will close this one so that we may centralize the content relating to the issue. I think the root cause for this may actually be #1753, based on the file count. If you feel that this issue is not in fact a duplicate, please feel free to re-open it. If you have additional information to share, please add it to the new issue. Thank you for reporting this! |
The exact command to reproduce the issue:
minikube start --mount-string /my/packages:/data/packages --mount
The full output of the command that failed:
Minikube starts and it prints
Creating mount /my/packages:/data/packages
,but when ssh'ing minikube (via
minikube ssh
) thenls
into/data/packages
, I can see that the directory is empty (of course/my/packages
is not empty).The output of the
minikube logs
command:The operating system version:
Using minikube v1.0.1
OS:
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
The text was updated successfully, but these errors were encountered: