Skip to content
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.

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

Prevent conflicts between multiple containers with the same name on the same network #86

Open
simonbru opened this issue Feb 27, 2020 · 0 comments

Comments

@simonbru
Copy link
Contributor

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.

@simonbru 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant