-
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
feature request: mount host volumes into docker driver via docker -v
#7604
Comments
Hey @ptramsey thanks for opening this issue -- this seems like a reasonable feature request. If anybody would be interested in working on this, please comment here! |
docker -v
Currently we are mounting the i.e. use this host directory, for getting things into the container ? See e.g. Mounting the See #6788 And #5012 |
Having the ability to specify arbitrary directories that aren't /var, though, is useful, and I would be surprised if people aren't already depending on that functionality, since the hyperkit driver on macos has it. Also, the virtualbox driver by default mounts /Users on macos and windows, and mounts /home to /hosthome on linux. If people are concerned about mounting /home itself, to the extent that we think it should be completely disallowed (rather than just being a warning), it seems like this feature request could still be accomplished with that change. After all, the feature request doesn't refer to mounting /home anyway --- the example it presents is of mounting a specific home directory (that isn't /home/minikube). |
Agree, adding the possibility to add mounts in the docker/podman driver would be a nice feature. |
/assign |
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. |
/remove-lifecycle stale |
bump |
Any progress on this? I stumbled upon this problem. It feels so hard to use Kubernetes local volumes without this feature. |
@vincent-163 yes, this was fixed and merged a while ago #8159 |
Steps to reproduce the issue:
This is a feature request; there's no failed command here to document. That said:
It would be really nice if the docker vm-driver allowed mapping paths from the local filesystem into the minikube container, using docker's volume binding functionality. E.g.,
... which would internally call something like,
As it is, despite running without virtualization on linux (which has a noticeable performance advantage), we're stuck using nfs or 9p to mount host paths inside minikube, both of which are slower (the latter of which is much slower) than just mapping the path directly via docker.
The text was updated successfully, but these errors were encountered: