You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All containers connected to a specific network share a common DNS namespace, which may lead to confusing conflicts.
Exemple: my frontend container/service is connected to the default network AND the pontsun network. It tries to proxy requests to the backend container/service, but the backend domain name resolves to another backend container from another project that is also part of the pontsun network.
To prevent this issue, we could give an explicit name to the default network (e.g. myproject) and use FQDNs (e.g. backend.myproject) in configuration files such as webpack.config.js.
The text was updated successfully, but these errors were encountered:
simonbru
changed the title
Use fully qualified domain names for services
Prevent conflicts between multiple containers with the same name on the same network
Jan 12, 2022
All containers connected to a specific network share a common DNS namespace, which may lead to confusing conflicts.
Exemple: my
frontend
container/service is connected to the default network AND the pontsun network. It tries to proxy requests to thebackend
container/service, but thebackend
domain name resolves to anotherbackend
container from another project that is also part of the pontsun network.To prevent this issue, we could give an explicit name to the default network (e.g.
myproject
) and use FQDNs (e.g.backend.myproject
) in configuration files such aswebpack.config.js
.The text was updated successfully, but these errors were encountered: