Skip to content

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

Open
@simonbru

Description

@simonbru

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions