# Where the configuration is stored elasticsearch in docker container

**URL:** <https://discuss.elastic.co/t/where-the-configuration-is-stored-elasticsearch-in-docker-container/301787>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Tags:** docker\
**Created:** [April 6, 2022, 5:23pm UTC](https://discuss.elastic.co/t/where-the-configuration-is-stored-elasticsearch-in-docker-container/301787 "2022-04-06T17:23:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![INS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ins/32/92827_2.png) [@INS](https://discuss.elastic.co/u/INS)\
**Post date:** [April 6, 2022, 5:23pm UTC](https://discuss.elastic.co/t/where-the-configuration-is-stored-elasticsearch-in-docker-container/301787/1 "2022-04-06T17:23:42Z")

</div>

Hi  
I'm trying to understand where is stored configuration when I've created node by docker compose? It was set only as environment variable?  
an example my config:

```auto
 es_data_hdd_9_1:
    image: pri_rep/elk-docker/elasticsearch/elasticsearch:8.1.0

    container_name: es_data_hdd_9_1
    environment:
      - node.name=es_data_hdd_9_1
      - xpack.ml.enabled=false
      - xpack.security.enabled=true
      - xpack.security.http.ssl.enabled=false
      - xpack.security.http.ssl.key=certs/es_data_hdd_9_1/es_data_hdd_9_1.key
      - xpack.security.http.ssl.certificate_authorities=certs/ca/ca.crt
      - xpack.security.http.ssl.certificate=certs/es_data_hdd_9_1/es_data_hdd_9_1.crt
      - xpack.security.transport.ssl.enabled=true
      - xpack.security.transport.ssl.verification_mode=certificate
      - xpack.license.self_generated.type=basic
      - xpack.security.transport.ssl.certificate_authorities=certs/ca/ca.crt
      - xpack.security.transport.ssl.certificate=certs/es_data_hdd_9_1/es_data_hdd_9_1.crt
      - xpack.security.transport.ssl.key=certs/es_data_hdd_9_1/es_data_hdd_9_1.key
      - ELASTIC_USERNAME=elastic
      - ELASTIC_PASSWORD=
      - cluster.name=elk_cluster
      - discovery.seed_hosts=es_master_1_1,es_master_2_1,es_master_1_2,es_master_2_2,es_master_1_3,es_master_2_3,es_data_ssd_3_1_ingest,es_data_ssd_1_1,es_data_ssd_2_1,es_data_ssd_3_1,es_data_ssd_4_1
      - cluster.initial_master_nodes=es_master_1_1,es_master_2_1,es_master_1_2,es_master_2_2,es_master_1_3,es_master_2_3
      - bootstrap.memory_lock=true
      - ingest.geoip.downloader.enabled=false
      - node.roles=data_cold

```

I've already checked `more ./usr/share/elasticsearch/config/elasticsearch.yml`  
but this is not that place....

```auto
more elasticsearch.yml
cluster.name: "docker-cluster"
network.host: 0.0.0.0

```

also when I'm checking in dev tool over `GET /_cluster/settings`  
I got

```auto
{
  "persistent" : { },
  "transient" : { }
}

```

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [April 19, 2022, 12:17pm UTC](https://discuss.elastic.co/t/where-the-configuration-is-stored-elasticsearch-in-docker-container/301787/2 "2022-04-19T12:17:34Z")

</div>

This forum is dedicated to the ECK operator so you maybe not the best place for your docker-compose question.

But any configuration you apply via environment variables will be picked up by the Elasticsearch process. They will not be replicated into one of the configuration files and they are also not part of the API based `_cluster/settings`.  
If you want to check whether a setting you configured has taken or not you can check the log files or in some cases there are dedicated APIs like for example for the certificate settings you can check [SSL certificate API | Elasticsearch Guide [8.1] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-ssl.html)

Hope this help.s

---

<div class="post-metadata">

**Author:** ![INS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ins/32/92827_2.png) [@INS](https://discuss.elastic.co/u/INS)\
**Post date:** [April 21, 2022, 3:52pm UTC](https://discuss.elastic.co/t/where-the-configuration-is-stored-elasticsearch-in-docker-container/301787/3 "2022-04-21T15:52:15Z")

</div>

Yeap, in container I've already found by **printenv** command

---

<div class="post-metadata">

**Author:** ![Doc\_Kaos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/doc_kaos/32/53671_2.png) [@Doc\_Kaos](https://discuss.elastic.co/u/Doc_Kaos)\
**Post date:** [May 4, 2022, 3:53pm UTC](https://discuss.elastic.co/t/where-the-configuration-is-stored-elasticsearch-in-docker-container/301787/4 "2022-05-04T15:53:19Z")

</div>

> [@pebrc](#):
>
> But any configuration you apply via environment variables will be picked up by the Elasticsearch process. They will not be replicated into one of the configuration files and they are also not part of the API based `_cluster/settings` .

😮 So `_cluster/settings` is not authoritative? Is it just basically: These settings may or may not be correct, likely they are not ... but they may be ...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 1, 2022, 3:53pm UTC](https://discuss.elastic.co/t/where-the-configuration-is-stored-elasticsearch-in-docker-container/301787/5 "2022-06-01T15:53:36Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.