# Some networks were defined but are not used by any service: elastic

**URL:** <https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [November 29, 2021, 6:39pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480 "2021-11-29T18:39:50Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![iruushi\_lol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iruushi_lol/32/97797_2.png) [@iruushi\_lol](https://discuss.elastic.co/u/iruushi_lol)\
**Post date:** [November 29, 2021, 6:39pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/1 "2021-11-29T18:39:50Z")

</div>

hey, i have a little problem with elastic, i have a error message : some networks were defined but are not used by any service: elastic, i have install kibana and this error appeared. i want to create ELK server on docker. but when i look in docker ps -a i don't have my nodes, i have launch docker-compose up -d --remove-orphans but i noticed that this command has deleted my nodes.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 29, 2021, 8:32pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/2 "2021-11-29T20:32:28Z")

</div>

Welcome to our community! 😃

It'd be useful if you could share the various config files you are using to try to make this work.

---

<div class="post-metadata">

**Author:** ![iruushi\_lol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iruushi_lol/32/97797_2.png) [@iruushi\_lol](https://discuss.elastic.co/u/iruushi_lol)\
**Post date:** [November 29, 2021, 8:39pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/3 "2021-11-29T20:39:51Z")

</div>

i fail my config this problem is resolute, but now i have a problem with kibana i have an error 64

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/3/e33ff14f9219016ec91a7b50b85839bcc5c6cc26.png)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 29, 2021, 8:46pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/4 "2021-11-29T20:46:51Z")

</div>

Please don't post pictures of text, logs or code. They are difficult to read, impossible to search and replicate (if it's code), and some people may not be even able to see them 🙂

---

<div class="post-metadata">

**Author:** ![iruushi\_lol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iruushi_lol/32/97797_2.png) [@iruushi\_lol](https://discuss.elastic.co/u/iruushi_lol)\
**Post date:** [November 29, 2021, 8:48pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/5 "2021-11-29T20:48:11Z")

</div>

okay it's a log start kibana

docker-compose.yml

```auto
version: '2.2'
services:
  kibana:
     image: docker.elastic.co/kibana/kibana:7.15.2
     volumes:
       - ./kibana.yml:/usr/share/kibana/config/kibana.yml
     environment:
       SERVER_NAME: kibana.example.org
       ELASTICSEARCH_HOSTS: '["http://es01:9200","http://es02:9200","http://es03:9200"]'

  es01:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.15.2
    container_name: es01
    environment:
      - node.name=es01
      - cluster.name=es-docker-cluster
      - discovery.seed_hosts=es02,es03
      - cluster.initial_master_nodes=es01,es02,es03
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - data01:/usr/share/elasticsearch/data
    ports:
      - 9200:9200
    networks:
      - elastic
  es02:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.15.2
    container_name: es02
    environment:
      - node.name=es02
      - cluster.name=es-docker-cluster
      - discovery.seed_hosts=es01,es03
      - cluster.initial_master_nodes=es01,es02,es03
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - data02:/usr/share/elasticsearch/data
    networks:
      - elastic
  es03:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.15.2
    container_name: es03
    environment:
      - node.name=es03
      - cluster.name=es-docker-cluster
      - discovery.seed_hosts=es01,es02
      - cluster.initial_master_nodes=es01,es02,es03
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1

```

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [November 29, 2021, 9:19pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/6 "2021-11-29T21:19:09Z")

</div>

What is the content of the file `./kibana.yml` that you are mapping as `/usr/share/kibana/config/kibana.yml` ?

There is something wrong with this file, are you sure this file is a Kibana configuration file?

From your error it seems to be trying to load configs from your `docker-compose.yml` file, you can see that it says that `version`, `services.kibana.image` and `services.kibana.volumes` are unknown configurations for kibana, those are the first lines of your `docker-compose.yml` file.

---

<div class="post-metadata">

**Author:** ![iruushi\_lol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iruushi_lol/32/97797_2.png) [@iruushi\_lol](https://discuss.elastic.co/u/iruushi_lol)\
**Post date:** [November 29, 2021, 9:21pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/8 "2021-11-29T21:21:56Z")

</div>

kibana.yml

```auto
version: '2'
services:
  kibana:
    image: docker.elastic.co/kibana/kibana:7.15.2
    volumes:
      - ./kibana.yml:/usr/share/kibana/config/kibana.yml

```

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [November 29, 2021, 9:25pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/9 "2021-11-29T21:25:06Z")

</div>

This file is wrong, it is not a Kibana configuration file, it is just part of docker-compose file.

Where did you get this from? You should pass a valid configuration to Kibana, only if you need to change anything from the default configuration.

Remove the `volumes` line below from the kibana service in your docker-compose and see if it starts.

```auto
     volumes:
       - ./kibana.yml:/usr/share/kibana/config/kibana.yml

```

---

<div class="post-metadata">

**Author:** ![iruushi\_lol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iruushi_lol/32/97797_2.png) [@iruushi\_lol](https://discuss.elastic.co/u/iruushi_lol)\
**Post date:** [November 29, 2021, 9:31pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/10 "2021-11-29T21:31:01Z")

</div>

I need modify the file kibana.yml, to make a good configuration ?

kibana start without the volume.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [November 29, 2021, 10:38pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/11 "2021-11-29T22:38:48Z")

</div>

You do not need to mount a local `kibana.yml` unless you have some specific configuration that you want to change.

I would suggest that you take a look at this [part of the documentation](https://www.elastic.co/guide/en/elastic-stack-get-started/current/get-started-docker.html#run-stack-docker) with an example of a `docker-compose.yml` to run an Elasticsearch cluster.

As you can see, there is no need to mount a volume with the `kibana.yml` file.

```auto
  kib01:
    image: docker.elastic.co/kibana/kibana:7.15.2
    container_name: kib01
    ports:
      - 5601:5601
    environment:
      ELASTICSEARCH_URL: http://es01:9200
      ELASTICSEARCH_HOSTS: '["http://es01:9200","http://es02:9200","http://es03:9200"]'
    networks:
      - elastic

```

This other [part of the documentation](https://www.elastic.co/guide/en/kibana/current/docker.html#configuring-kibana-docker) explains that if you need you can configure Kibana using a bind-mount.

---

<div class="post-metadata">

**Author:** ![iruushi\_lol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iruushi_lol/32/97797_2.png) [@iruushi\_lol](https://discuss.elastic.co/u/iruushi_lol)\
**Post date:** [November 30, 2021, 6:43pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/12 "2021-11-30T18:43:36Z")

</div>

hey, thanks for helping, now i have a web interface. if i want logs i need install logstack ?

---

<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:** [December 28, 2021, 6:44pm UTC](https://discuss.elastic.co/t/some-networks-were-defined-but-are-not-used-by-any-service-elastic/290480/13 "2021-12-28T18:44:10Z")

</div>

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