How to Quickly Resolve Docker Network IP Address Conflicts

Understanding Docker network IP address conflicts

When multiple containers on the same Docker host are attached to the same user‑defined network, Docker may assign identical IPv4 addresses. This typically occurs because the network’s IPAM pool overlaps or because containers are manually given static IPs that clash.

1. Identify duplicate IP addresses

List all networks and inspect each to find overlapping IP assignments.

docker network ls
docker inspect <code>network_name</code>

In the JSON output, look for the IPAM.Config section of each container and note any repeated IPv4Address values.

2. Stop one of the conflicting containers

Stopping a container releases its IP address back to the pool.

docker stop <code>container_name</code>

3. Reassign a unique IP address

If both containers must remain running, assign a new address that is inside the network’s subnet but not already used.

docker exec -it <code>container_name</code> /bin/bash
ip addr show               # verify current address
ip addr add <code>new_ip_address</code>/<code>subnet_mask</code> dev eth0
exit

Replace new_ip_address and subnet_mask with values that fit the network’s CIDR (e.g., 172.20.0.10/16).

4. Clean the Docker environment (optional)

If the conflict persists or the network state is corrupted, you can prune containers, images, and networks, then restart the Docker daemon.

Stop all containers docker stop $(docker ps -aq) Remove all containers docker rm $(docker ps -aq) Remove all images docker rmi -f $(docker images -q) Prune unused networks docker network prune -f Restart Docker service

systemctl restart docker

To prevent future conflicts, allocate each container a distinct static IP (or let Docker assign dynamically), avoid mapping multiple containers to the same host port, and consider using network‑level access controls.