-
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
Directories not persisted across reboots #414
Comments
Only dirs under /mnt/sda1 will persist. You can either change your hostPath declaration or symink /data to /mnt/sda1/data perhaps? |
Yeah, we should probably create a simple to use persisted directory (maybe /data?), and document it. Any opinions on which to use? |
Host paths are discouraged in general. Wonder if we can set up a persistent volume (even if that is a hostPath PV) via minikube to make this a bit more transparent to users? |
Thanks. I just found this discussion about pv and pvc: #2 |
@jimmidyson @dlorenc: Is |
No, it's just a disk that is persisted across "minikube stop" commands, but not "minikube delete". On some systems "/Users" is automatically mounted in from the host, but not everywhere yet. We're making that more consistent before documenting it. |
I've got mongodb running on minikube but when I
minikube stop
and thenminikube start
all the data that was in mongodb is lost. I have the pod mounting a host volume located at/data/mdb
. The same thing is happening with elasticsearch.I am opening this issue at the request of @dlorenc on the slack channel.
The text was updated successfully, but these errors were encountered: