# Docker compose network

**URL:** <https://forums.docker.com/t/docker-compose-network/145092>\
**Category:** General\
**Tags:** docker, docker-compose, networking\
**Created:** [November 21, 2024, 7:21pm UTC](https://forums.docker.com/t/docker-compose-network/145092 "2024-11-21T19:21:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![proger002](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/proger002/32/53920_2.png) [@proger002](https://forums.docker.com/u/proger002)\
**Post date:** [November 21, 2024, 7:21pm UTC](https://forums.docker.com/t/docker-compose-network/145092/1 "2024-11-21T19:21:26Z")

</div>

Hello, colleagues!

I encountered a problem when setting up Docker networks on an Ubuntu Server 24.04 server running as a virtual machine on ESXi.  
Docker is installed on the server, and the Docker service is actively running. When starting the docker compose, one of the networks cannot be created. All other networks are created without problems, but one specific network ends the creation with an error:  
Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network

Docker version 27.3.1, build ce12230

The output of docker network ls shows standard networks (bridge, host, none) and additional ones that are created for containers.

The ip link show docker0 command shows that the docker0 interface is in the state:  
docker0: \<NO-CARRIER,BROADCAST,MULTICAST,UP\> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default.

The Docker service starts successfully, but there is a conflict when creating a subnet for one of the networks.

How can I solve the problem with the network and the docker0 interface to avoid a subnet conflict? Thanks in advance for your help!

---

<div class="post-metadata">

**Author:** ![meyay](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/meyay/32/34000_2.png) [@meyay](https://forums.docker.com/u/meyay)\
**Post date:** [November 21, 2024, 7:34pm UTC](https://forums.docker.com/t/docker-compose-network/145092/2 "2024-11-21T19:34:42Z")

</div>

Does this post help? [https://forums.docker.com/t/docker-change-default-ip-range-for-all-and-new-containers/144474/8](https://forums.docker.com/t/docker-change-default-ip-range-for-all-and-new-containers/144474/8)

If you change the bridge ip in `/etc/docker/daemon.json` (create the file if it doesn’t exist), make sure to stop the docker engine, remove the default bridge and docker0 interface, before restarting the docker engine again. It should re-create the interface and default bridge network.

---

<div class="post-metadata">

**Author:** ![proger002](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/proger002/32/53920_2.png) [@proger002](https://forums.docker.com/u/proger002)\
**Post date:** [November 22, 2024, 1:19am UTC](https://forums.docker.com/t/docker-compose-network/145092/3 "2024-11-22T01:19:24Z")

</div>

Thank you so much! You saved me.  
This helped me [Docker - change default ip range for all and new containers - #8 by meyay](https://forums.docker.com/t/docker-change-default-ip-range-for-all-and-new-containers/144474/8)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/docker/original/3X/d/4/d4fbccd46c81bfcffe9822e20e17736d946fa821.png) [@system](https://forums.docker.com/u/system)\
**Post date:** [December 2, 2024, 1:20am UTC](https://forums.docker.com/t/docker-compose-network/145092/4 "2024-12-02T01:20:02Z")

</div>

Closed on December 2, 2024, 1:20am UTC

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