Skip to content

Docs: Updating Different Networks Container Solving #663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mageddo merged 1 commit into from
Dec 18, 2025
Merged

Docs: Updating Different Networks Container Solving #663

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions docs/content/2-features/docker-different-networks-solving/_index.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,14 @@ You can [click here][1] to see a pratical working sample.
The following table describles the possible scenarios involving docker container networks, some scenarios won't work,
you can consider enable [DPS Docker Network feature][1] so all contains will always be able to talk with each other.

| DPS Container Network | Client Container Network | Target Container Network | Result | Description |
|-----------------------|--------------------------|--------------------------|:------------:|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| any bridge network | any bridge network | any bridge network | OK | Everything works fine when all the networks are using bridge driver, no problem if the networks are different |
| Network x | Network x | Network x | OK | Even with restrictive networks (like overlay driver) the resolution will work, since all containers are connected to this same network. |
| Network a, Network b | Network a | Network b | PARTIALLY OK | Resolution is OK but Client Container can't ping Target Container. The minimal requirement is that client must be on the same network which DPS so the client will able to query DPS, then client also need to be on the same network which the target container, so it will be able to ping after solve the hostname. |
| Network a | Network b | Network b | NOK | Client container won't be able to talk with DPS |
| DPS Container Network | Client | Client Network | Target Container Network | Result | Description |
|-----------------------|-----------|--------------------|--------------------------|:------------:|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Any bridge network | Container | any bridge network | any bridge network | OK | Everything works fine when all the networks are using bridge driver, no problem if the networks are different |
| Network x | Container | Network x | Network x | OK | Even with restrictive networks (like overlay driver) the resolution will work, since all containers are connected to this same network. |
| Network a, Network b | Container | Network a | Network b | PARTIALLY OK | Resolution is OK but Client Container can't ping Target Container. The minimal requirement is that client must be on the same network which DPS so the client will able to query DPS, then client also need to be on the same network which the target container, so it will be able to ping after solve the hostname. |
| Network a | Container | Network b | Network b | NOK | Client container won't be able to talk with DPS |
| Any bridge network | Host | Any | any bridge network | OK | Host can ping to DPS and Ping the target solved container IP |
| Any bridge network | Host | Any | Not on a Bridge Network | PARTIALLY OK | Host can ping to DPS but can't Ping the target solved container IP |
| Network a | Host | Any | Any | FAIL | Host can't ping to DPS, so DNS resolution won't work on the host Machine, you can bypass that by publishing DPS container port to the host machine but is only possible on Linux |

[1]: {{%relref "2-features/dps-network-resolution/_index.md" %}}