IdealPanda97 Is your user id 1000? If not then this maybe the reason and chown -R 1000:1000 may help. Elasticsearch in the docker runs with user 1000. Another reason maybe some other elasticsearch process or docker running on your machine and holding the lock in the data folder. If there are any then please try stopping them. If neither of the above helps then there is an option of manually deleting .lock files from the elastic data folder. Of course the data should be backed up before this. https://stackoverflow.com/questions/28932178/elasticsearch-failed-to-obtain-node-lock-is-the-following-location-writable
IdealPanda97 It seems Elasticsearch fails to start, can you list the contents of
/opt/trains/data/elastic/nodes ? According to the logs this looks like either a permission or a lock issue...
I was helped by running from user 1000 and the command "http_proxy= docker-compose -f /opt/trainz/docker-compose.html up"
AppetizingMouse58 SuccessfulKoala55 Thank you so much!
IdealPanda97 Ok, I see. Can you please run the following command, then restart the docker-compose and see if it makes any difference?
sudo chown -R 1000:1000 /opt/trains
Hi IdealPanda97 , can you please check your available disk space and available RAM? According to the logs all the services (Elastic, Mongo, Redis) fail to start
SuccessfulKoala55 Sure. I can attach an archive with the elastic folder if necessary. But it weighs 500MB
AppetizingMouse58 There should be enough space on the disks
AppetizingMouse58 I made my user the owner (sudo chown liz:liz -R /opt/trains/), but the problem still remains.