Skip to content
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

Closed
Nalum opened this issue Jul 27, 2016 · 6 comments
Closed

Directories not persisted across reboots #414

Nalum opened this issue Jul 27, 2016 · 6 comments

Comments

@Nalum
Copy link

Nalum commented Jul 27, 2016

I've got mongodb running on minikube but when I minikube stop and then minikube 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.

@jimmidyson
Copy link
Member

Only dirs under /mnt/sda1 will persist. You can either change your hostPath declaration or symink /data to /mnt/sda1/data perhaps?

@dlorenc
Copy link
Contributor

dlorenc commented Jul 28, 2016

Yeah, we should probably create a simple to use persisted directory (maybe /data?), and document it. Any opinions on which to use?

@jimmidyson
Copy link
Member

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?

@Nalum
Copy link
Author

Nalum commented Jul 28, 2016

Thanks. I just found this discussion about pv and pvc: #2

@Nalum
Copy link
Author

Nalum commented Jul 29, 2016

@jimmidyson @dlorenc: Is /mnt/sda1 mounted from the host system onto the cluster vm?

@dlorenc
Copy link
Contributor

dlorenc commented Jul 29, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants