Handling IP Conflicts in Docker

This guide explains how to configure Docker to avoid conflicts with university campus networks and VPNs (typically 172.x.x.x) by moving Docker's network pools to the 192.168 range.

Why is this necessary?

Many university networks, campus firewalls, and internal resources use the 172.x.x.x range. If Docker uses the same addresses, your computer won't be able to distinguish between a local container and a university server (such as a library database, lab resource, or internal tool).

This conflict occurs regardless of your connection method:

  • On-campus: When connected to the university network via Ethernet or Eduroam.
  • Off-campus: When connected via a VPN to access restricted university resources.

Moving Docker to a safe IP range ensures seamless connectivity across different campuses and remote locations.

1. IP Address Strategy

To easily distinguish between environments during troubleshooting and avoid common home router ranges (like 192.168.1.x):

  • Local (Docker Desktop): Uses the higher range (128) to remain distinct from common public Wi-Fi and home setups.
  • Server/VPS (Docker Engine): Uses the lower range (64), which rarely conflicts with cloud providers' internal networks.

2. Configuration: Docker Desktop (Windows, Mac, or Linux GUI)

If you are using the graphical interface of Docker Desktop:

  1. Open Settings (gear icon).
  2. Navigate to Docker Engine.
  3. Update the JSON configuration:
‌‌‌‌‌

Click Apply & Restart after making changes.

3. Configuration: Docker Engine (Native Linux Server)

For native Linux installations (e.g., Ubuntu, Debian, RHEL), edit the daemon configuration file:

‌‌‌‌‌

Paste the following configuration:

‌‌‌‌‌

Restart the Docker service to apply changes:

‌‌‌‌‌

4. Post-Setup and Migration

Verify New Settings

Run this command to ensure the default bridge has changed its IP:

‌‌‌‌‌

Update Existing Projects (Migration)

To force all projects to migrate to the new IP range immediately, run these commands:

  1. Stop all running containers:

    ‌‌‌‌‌

  2. Remove all old networks:

    ‌‌‌‌‌

  3. Restart your projects:

    Navigate to your project directory and start the containers using the appropriate Docker Compose command for the project.

    Example:

    ‌‌‌‌‌

Identify "Legacy" Networks

To check if any networks are still residing in the old 172.x.x.x range:

‌‌‌‌‌

Why This Setup?

  1. Troubleshooting: If you see an IP starting with 128, you know it's your local machine. If you see 64, it's the VPS.
  2. Safety: 192.168.64+ avoids most common home routers (which typically use 192.168.0.x or 1.x).
  3. Universal Connectivity: Ensures your Docker environment and university network can coexist, whether you are on campus or working remotely via VPN.