From f782858a453ac0d47012923b849a4c1dddef46d9 Mon Sep 17 00:00:00 2001 From: Tianon Gravi Date: Tue, 24 Nov 2015 09:47:09 -0800 Subject: [PATCH] Fix cassandra volume path --- cassandra/content.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cassandra/content.md b/cassandra/content.md index ab8300cc..89fc8a8b 100644 --- a/cassandra/content.md +++ b/cassandra/content.md @@ -141,10 +141,10 @@ The Docker documentation is a good starting point for understanding the differen 2. Start your `%%REPO%%` container like this: ```console - $ docker run --name some-%%REPO%% -v /my/own/datadir:/var/lib/cassandra/data -d %%REPO%%:tag + $ docker run --name some-%%REPO%% -v /my/own/datadir:/var/lib/cassandra -d %%REPO%%:tag ``` -The `-v /my/own/datadir:/var/lib/cassandra/data` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/var/lib/cassandra/data` inside the container, where Cassandra by default will write its data files. +The `-v /my/own/datadir:/var/lib/cassandra` part of the command mounts the `/my/own/datadir` directory from the underlying host system as `/var/lib/cassandra` inside the container, where Cassandra by default will write its data files. Note that users on host systems with SELinux enabled may see issues with this. The current workaround is to assign the relevant SELinux policy type to the new data directory so that the container will be allowed to access it: