ES runs in it's docker image not as root, but as user elasticsearch (UID 1000). If you run the docker-compose as root, the docker-persistence directory structure is created for root. If you change ownership of the es directory, elasticsearch will start up fine.
ES version is 7.6.0
Docker Compose is 1.25.5
sudo curl -L "https://github.com/docker/compose/releases/download/1.25.5/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
root@testvm:/var/harness-docker-compose# git status
On branch develop
Your branch is up to date with 'origin/develop'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
harness-docker-compose/
nothing added to commit but untracked files present (use "git add" to track)
root@testvm:/var/harness-docker-compose#
When trying the one-line docker-compose version, elasticsearch fails because it cannnot access it's data directory:
ES runs in it's docker image not as root, but as user elasticsearch (UID 1000). If you run the docker-compose as root, the docker-persistence directory structure is created for root. If you change ownership of the es directory, elasticsearch will start up fine.
https://github.com/actionml/harness/blob/develop/docker/docker-compose.yml does not have this issue, because the ES data directory is not mapped on the host.
ES version is 7.6.0 Docker Compose is 1.25.5
sudo curl -L "https://github.com/docker/compose/releases/download/1.25.5/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
Docker install:
Here is the output of status data:
I used the guide at https://actionml.com/docs/harness_container_guide to set up harness.
git clone https://github.com/actionml/harness-docker-compose.git