-
Notifications
You must be signed in to change notification settings - Fork 16.9k
Zookeeper doesn't deploy into virtualbox minikube #976
Comments
I'm having a similar issue, but how have you confirmed that this is a VirtualBox bug? Have you tried other vm driver? |
@aschepis can you please log this issue against minikube? I believe the it should use host path PVs. |
you can close this issue. it is not specific to the chart |
I'm hitting this problem too, and I can't figure out where to put the emptyDir: {} to hack it. Also, I can't find a corresponding issue in minikube, was one logged? |
This is the relevant minikube issue, though the underlying problem appears to be in k8s: kubernetes/minikube#956 |
See also: kubernetes/kubernetes#2630 |
Another way to make this work is to remove the "runAsUser", or change to runAsUser: 0 in the ss.yaml file. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d 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. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Virtualbox appears to have an issue with mounting
hostPath
PVs in a writeable/accessible state. As a result, zookeeper fails to get started in minikubeI hacked my way around it by using
emptyDir: {}
for my datadir. not a great solution. I'm happy to open PR to fix if I can get some guidance on an approach that would be acceptable.Startup logs:
The text was updated successfully, but these errors were encountered: