-
Notifications
You must be signed in to change notification settings - Fork 279
Startup error #123
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
Comments
Before we step down from root, we adjust permissions on cassandra/3.11/docker-entrypoint.sh Line 11 in b77e932
So, I'm not sure how this could fail. 😕 |
|
Those are both inside the container. |
I wasn't sure. Could it be that the docker image itself has wrong permissions? |
Cassandra starts okay, when I map a named volume instead of a volume on the host:
As I understand, I have to map a volume on the host to have data persistency?
|
Are you running on Docker for Windows, Docker for Mac, or Docker Toolbox
(and thus Docker Machine with vboxsf file share)?
Permissions in those environments are always a bit of a struggle.
|
I am running Docker in Vagrant VM ( Ubuntu 17.04 ). I noticed this:
|
Let's confirm a couple things: If you run it as normal, and attach to the container, can you see a /var/lib/cassandra ? If so, what are the permissions on it? |
UPDATE: I can confirm now that the problem is gone where I map a local directory OUTSIDE the directory which is mapped to the host machine. :) |
As mentioned in #48 (comment), the shared folder behavior could be circumvented by using NFS from the host into the VM instead of Vagrant's shared folders. (Even though the other issue references VBox, it's about the same behavior for Vagrant.) |
Thank you. My problem is solved by simply mapping the database to a folder outside the shared folders. I am fine with that. |
I am trying to start a cassandra node in docker with:
Every time this ends with the error:
ERROR [main] 2017-11-28 22:17:46,792 CassandraDaemon.java:752 - Has no permission to create directory /var/lib/cassandra/data
What should I do to enable the Daemon to make the directory?
The text was updated successfully, but these errors were encountered: