Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

Zookeeper doesn't deploy into virtualbox minikube #976

Closed
aschepis opened this issue Apr 28, 2017 · 10 comments
Closed

Zookeeper doesn't deploy into virtualbox minikube #976

aschepis opened this issue Apr 28, 2017 · 10 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@aschepis
Copy link

Virtualbox appears to have an issue with mounting hostPath PVs in a writeable/accessible state. As a result, zookeeper fails to get started in minikube

I 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:

2017-04-28T13:30:58.695403610Z ZK_MAX_CLIENT_CNXNS=60
2017-04-28T13:30:58.696127763Z ZK_MIN_SESSION_TIMEOUT= 4000
2017-04-28T13:30:58.696131577Z ZK_MAX_SESSION_TIMEOUT= 40000
2017-04-28T13:30:58.696134032Z ZK_HEAP_SIZE=256m
2017-04-28T13:30:58.696136340Z ZK_SNAP_RETAIN_COUNT=3
2017-04-28T13:30:58.696138699Z ZK_PURGE_INTERVAL=1
2017-04-28T13:30:58.696141223Z ENSEMBLE
2017-04-28T13:30:58.696143672Z server.1=zk-kafka-zookeeper-0.hs-zk-kafka-zookeeper.default.svc.cluster.local:2888:3888
2017-04-28T13:30:58.696146303Z Enviorment validation successful
2017-04-28T13:30:58.696158215Z Creating ZooKeeper configuration
2017-04-28T13:30:58.696161196Z Wrote ZooKeeper configuration file to /opt/zookeeper/conf/zoo.cfg
2017-04-28T13:30:58.699766539Z Creating ZooKeeper log4j configuration
2017-04-28T13:30:58.699829100Z Wrote log4j configuration to /opt/zookeeper/conf/log4j.properties
2017-04-28T13:30:58.699880471Z Creating ZooKeeper data directories and setting permissions
2017-04-28T13:30:58.701553986Z mkdir: cannot create directory '/var/lib/zookeeper': Permission denied
2017-04-28T13:30:58.704557792Z chown: cannot access '/var/lib/zookeeper/data': Permission denied
2017-04-28T13:30:58.709345143Z mkdir: cannot create directory '/var/lib/zookeeper': Permission denied
2017-04-28T13:30:58.710343958Z chown: cannot access '/var/lib/zookeeper/log': Permission denied
2017-04-28T13:30:58.710618048Z /usr/bin/zkGenConfig.sh: line 125: /var/lib/zookeeper/data/myid: Permission denied
2017-04-28T13:30:58.710661909Z Created ZooKeeper data directories and set permissions in /var/lib/zookeeper/data
2017-04-28T13:30:58.711457677Z Creating JVM configuration file
2017-04-28T13:30:58.711466891Z Wrote JVM configuration to /opt/zookeeper/conf/java.env
2017-04-28T13:30:58.717536771Z ZooKeeper JMX enabled by default
2017-04-28T13:30:58.718452575Z Using config: /usr/bin/../etc/zookeeper/zoo.cfg
2017-04-28T13:30:58.721629296Z mkdir: cannot create directory '/var/lib/zookeeper': Permission denied
@gducharme
Copy link

I'm having a similar issue, but how have you confirmed that this is a VirtualBox bug? Have you tried other vm driver?

@lachie83
Copy link
Contributor

@aschepis can you please log this issue against minikube? I believe the it should use host path PVs.

@aschepis
Copy link
Author

you can close this issue. it is not specific to the chart

@francisu
Copy link

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?

@francisu
Copy link

This is the relevant minikube issue, though the underlying problem appears to be in k8s: kubernetes/minikube#956

@francisu
Copy link

See also: kubernetes/kubernetes#2630

@francisu
Copy link

francisu commented Jul 3, 2017

Another way to make this work is to remove the "runAsUser", or change to runAsUser: 0 in the ss.yaml file.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 30, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

6 participants