Open AhmadShaik opened 11 months ago
Hi @AhmadShaik, The error you're seeing is not related to the port you changed, but rather related to the fact the ES cannot start for some reason. I believe this is due to the data folder not having the right permissions, specifically the ES data folder should be owned by 1000:1000 (as explained in step 9 here)
@jkhenning Im facing the same problem. We have docker group as 999
instead of 1000
, so I swapped guid with 999. I couldn't find docker user in /etc/passwd and 1000
is some organization admin user. ATM I have root:docker configuration. Should I have docker user configured?
Note that all works when data folder has +w permissions for all users
In general the issue of group 1000 is not something that can easily be changed (unrelated to clearml in this case) since as far as I know docker/ES depends on it
I have a similar problem.
@a1xs as far as I know this is an ES issue when run inside docker
@a1xs as far as I know this is an ES issue when run inside docker
Yes, this is a problem with elasticserch. I returned to the old working version.
I change the path from /usr/share/elasticsearch/data to /var/lib/elasticsearch/data and it works!
I am trying to run the clearml-server with one change from the default. Since my system is already using 8080, I changed that port to 9080 in the docker-compose.yml file. When I tried to run the application, I am getting server not available error in the UI. also in the terminal I am getting below error.
Here is my docker-compose.yml file.
Here is the docker log from clearml-elasticsearch
The system has 25 GB Ram and 2.5 TB free storage.
Hoe can I solve this error.