Esraa Madi
11/11/2022, 10:17 AMYannick
Aborting auto configuration because of config dir ownership mismatch. Config dir is owned by elasticsearch but auto-configuration directory would be owned by root
{"@timestamp":"2022-11-11T10:30:30.091Z", "log.level":"ERROR", "message":"fatal exception while booting Elasticsearch", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.Elasticsearch","elasticsearch.node.name":"elasticsearch-f8e9a7a0-daf0-4bce846a697d-11a5-414c-7666979l6kqg","elasticsearch.cluster.name":"docker-cluster","error.type":"java.lang.RuntimeException","error.message":"can not run elasticsearch as root"}
ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/docker-cluster.log
ERROR: Elasticsearch exited unexpectedly
In addition, when following their installation docs they talk about an authentication token that you need to provide when making requests. And thus I don't expect the request to succeed anyways, but in your case the service completely fails to start due to the above error.
Regarding not being allowed to enter dots in the names, you can convert the names according to the their docs:
If you cannot do this, for example because your orchestration platform forbids periods in environment variable names, then you can use an alternative style by converting the setting name as follows.
1. Change the setting name to uppercase
2. Prefix it withES_SETTING_
3. Escape any underscores () by duplicating them_
4. Convert all periods () to underscores (.
)_
For example,becomes-e bootstrap.memory_lock=true
.-e ES_SETTING_BOOTSTRAP_MEMORY__LOCK=true
auto-configuration directory would be owned by root
so we need to make sure this directory is not owned by root. Since you are using an image that is provided by elasticsearch it would be strange if they provide an image that doesn't start and thus I expect that we (in Orchest) automatically mount to a location in the Docker image that elasticsearch also uses for the auto-configuration
directory.
Maybe it helps to change the directory (possibly this page in the elasticsearch docs). We mount the following paths by default: /project-dir
, /data
Hope that helps!Rick Lamers
Yannick
.
as well, but would be good to check.Rick Lamers
Yannick
Rick Lamers
Esraa Madi
11/12/2022, 1:58 PMYannick
but still getting an error that i have to setup these variablesThat sucks... sadly I can't really help with this given that this is at the side of elastic. When setting up a custom Docker image for your service, you can also use Environments in Orchest. That way it should be easier to iterate on the custom image.
Rick Lamers