Skip to content

Commit af2711c

Browse files
mageddomageddo
authored
Docs: Updating Different Networks Container Solving (#663)
1 parent db2cc0a commit af2711c

File tree

1 file changed

+9
-6
lines changed
  • docs/content/2-features/docker-different-networks-solving

1 file changed

+9
-6
lines changed

‎docs/content/2-features/docker-different-networks-solving/_index.en.md‎

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,14 @@ You can [click here][1] to see a pratical working sample.
1111
The following table describles the possible scenarios involving docker container networks, some scenarios won't work,
1212
you can consider enable [DPS Docker Network feature][1] so all contains will always be able to talk with each other.
1313

14-
| DPS Container Network | Client Container Network | Target Container Network | Result | Description |
15-
|-----------------------|--------------------------|--------------------------|:------------:|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
16-
| 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 |
17-
| 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. |
18-
| 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. |
19-
| Network a | Network b | Network b | NOK | Client container won't be able to talk with DPS |
14+
| DPS Container Network | Client | Client Network | Target Container Network | Result | Description |
15+
|-----------------------|-----------|--------------------|--------------------------|:------------:|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
16+
| 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 |
17+
| 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. |
18+
| 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. |
19+
| Network a | Container | Network b | Network b | NOK | Client container won't be able to talk with DPS |
20+
| Any bridge network | Host | Any | any bridge network | OK | Host can ping to DPS and Ping the target solved container IP |
21+
| 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 |
22+
| 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 |
2023

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

0 commit comments

Comments
 (0)