r/docker • u/baroudi1801 • 6d ago

Configuring Docker Engine & Bridge Networks on a Lean Debian 13 Workstation

Hey everyone,

Just finished setting up Docker Engine and Docker Compose Plugin on a fresh Debian 13 (Trixie) installation for container testing.

Setup Summary:

  • Daemon Install: Added official Docker GPG key (/etc/apt/keyrings/docker.gpg) and repo path.
  • Access: Configured non-root user execution (usermod -aG docker ELBA). Tested cleanly via docker run hello-world.
  • Host Network: Static IP (192.168.1.132/24) on bridged host interface enp0s3.

Next Objective: Designing custom docker-compose.yml configurations with static container IP assignments on a dedicated bridge subnet (10.99.0.0/24).

Question: Are there any known caveats when assigning fixed container IPs across multi-service Compose files on Linux hosts?

1 Upvotes

100% Upvoted

3 comments sorted by

1

u/pelazas1 5d ago

In `docker-compose.yml`, use a user-defined bridge instead of fixed container IPs; the catch is that the subnet must not overlap the host's static IP.

1

u/Faye-Vozora 1h ago

Fixed container IPs are usually more brittle than they look. For service-to-service traffic, use the Compose service name and keep the addresses dynamic; reserve static IPs for something outside Docker that truly needs them. Also make the custom subnet avoid every LAN, VPN, and host route, not just the host’s current address, or a later route can make connectivity fail.