How to fix Error response from daemon: network with name mynetwork already exists in Docker

DockerBEGINNERLOWUpdated Dec 6, 2025· 270 views

This error occurs when you try to create a Docker network that already exists. The fix is simple: either use the existing network, remove it first, or check if it exists before creating.

Quick fix

Fixes Error response from daemon: network with name mynetwork already exists

docker network ls | grep mynetwork
  1. Check if the network already exists
  2. Use the existing network instead of creating a new one
  3. Remove the existing network
  4. Create network only if it doesn't exist
docker — error
docker network ls | grep mynetwork
Error response from daemon: network with name mynetwork already exists

What this error means

The "network with name already exists" error occurs when Docker tries to create a network but finds that a network with the same name is already registered in the Docker daemon. Every Docker network must have a unique name within the Docker host. This commonly happens in several scenarios: - Running `docker network create` multiple times with the same network name - Docker Compose tries to create its default network but it already exists from a previous run - Scripts or CI pipelines that create networks without checking if they already exist - A previous container or compose stack wasn't properly cleaned up The error is straightforward to resolve - you just need to either use the existing network, remove it, or add a check before creating.

Typical symptoms

  • docker network create command fails with 'network with name X already exists'
  • docker-compose up fails when trying to create its project network
  • CI/CD pipeline fails at network creation step
  • Scripts that worked before suddenly fail after partial runs
  • Error appears when restarting a docker-compose project

Common causes

  1. Running docker network create with a name that already exists
  2. Previous docker-compose run created the network and it wasn't removed
  3. A script or automation created the network in a previous run
  4. Orphaned network from a crashed or force-killed container
  5. Multiple docker-compose projects using the same network name

How to fix "Error response from daemon: network with name mynetwork already exists"

1Check if the network already exists

First, verify the network exists and inspect its details:

bash
docker network ls | grep mynetwork

To see full details of the existing network:

bash
docker network inspect mynetwork

This shows which containers are connected to it and its configuration.

2Use the existing network instead of creating a new one

If the network already exists and has the configuration you need, simply use it. In docker-compose.yml, you can reference an existing external network:

yaml
networks:
  mynetwork:
    external: true

For docker run, just connect to the existing network:

bash
docker run --network mynetwork myimage
3Remove the existing network

If you want to recreate the network fresh, remove the existing one first:

bash
docker network rm mynetwork

If containers are still connected to the network, you'll need to disconnect or stop them first:

bash
# See what's connected
docker network inspect mynetwork --format '{{range .Containers}}{{.Name}} {{end}}'

# Disconnect a container
docker network disconnect mynetwork container_name

# Or stop all connected containers
docker stop $(docker network inspect mynetwork -f '{{range .Containers}}{{.Name}} {{end}}')

# Then remove the network
docker network rm mynetwork
4Create network only if it doesn't exist

The best approach for scripts and automation is to check before creating. Use this one-liner:

bash
docker network inspect mynetwork >/dev/null 2>&1 || docker network create mynetwork

This inspects the network (silently) and only creates it if the inspect command fails.

For more robust scripts, use a filter with exact matching:

bash
if [ -z "$(docker network ls --filter name=^mynetwork$ --format '{{.Name}}')" ]; then
  docker network create mynetwork
fi

The ^mynetwork$ regex ensures exact matching (not partial matches like "mynetwork2").

5Clean up with docker network prune

If you have multiple orphaned networks causing issues, clean them all up:

bash
docker network prune

This removes all networks not used by at least one container. Add -f to skip the confirmation prompt:

bash
docker network prune -f

Warning: This removes ALL unused networks, so make sure you don't need them.

6Handle docker-compose network conflicts

Docker Compose creates networks named <project>_default or <project>_<network>. If you get conflicts:

Option 1: Bring down the old project properly:

bash
docker-compose down

Option 2: Use a different project name:

bash
docker-compose -p newproject up

Option 3: Force recreate everything:

bash
docker-compose up --force-recreate

Advanced notes

Handling in CI/CD pipelines: Always use the "create if not exists" pattern in CI/CD to make pipelines idempotent:

bash
docker network inspect mynetwork >/dev/null 2>&1 || docker network create --driver bridge mynetwork

Returning the network ID: If your script needs the network ID regardless of whether it was just created:

bash
docker network inspect mynetwork --format '{{.Id}}' 2>/dev/null || docker network create mynetwork

Docker Compose external networks: When multiple Compose projects need to share a network, create it externally once:

bash
docker network create shared_network

Then in all docker-compose.yml files:

yaml
networks:
  shared_network:
    external: true

Force disconnect stuck containers: Sometimes a container endpoint gets stuck in a network after a crash. Force disconnect with:

bash
docker network disconnect --force mynetwork container_name

Restarting Docker daemon: As a last resort for stuck networks that won't delete, restart the Docker daemon:

bash
sudo systemctl restart docker

This clears any corrupted network state. Note: this will stop all running containers.

Windows/Mac with Docker Desktop: On Docker Desktop, you can also reset Docker to factory defaults from the GUI if network issues persist. Go to Settings > Reset > Reset to factory defaults. This removes all containers, images, and networks.

Frequently asked questions

What does "Error response from daemon: network with name mynetwork already exists" mean?
The "network with name already exists" error occurs when Docker tries to create a network but finds that a network with the same name is already registered in the Docker daemon. Every Docker network must have a unique name within the Docker host. This commonly happens in several scenarios: - Running docker network create multiple times with the same network name - Docker Compose tries to create its default network but it already exists from a previous run - Scripts or CI pipelines that create networks without checking if they already exist - A previous container or compose stack wasn't properly cleaned up The error is straightforward to resolve - you just need to either use the existing network, remove it, or add a check before creating.
How do I fix "Error response from daemon: network with name mynetwork already exists"?
This error occurs when you try to create a Docker network that already exists. The fix is simple: either use the existing network, remove it first, or check if it exists before creating.
What causes "Error response from daemon: network with name mynetwork already exists"?
Running docker network create with a name that already exists Previous docker-compose run created the network and it wasn't removed A script or automation created the network in a previous run
Is the "Error response from daemon: network with name mynetwork already exists" error serious?
It is a low-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading