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

Dynamic Docker network IP range #4878

Open
Abbas-b-b opened this issue Dec 1, 2022 · 1 comment
Open

Dynamic Docker network IP range #4878

Abbas-b-b opened this issue Dec 1, 2022 · 1 comment

Comments

@Abbas-b-b
Copy link

Summary

The default ipv4 subnet (172.22.1.0/24) may already be used with other Docker networks.
It'll be more convenient to find an available address to prevent the following error.
ERROR: Pool overlaps with other one on this address space

Motivation

This will eliminate Pool overlaps error on docker compose up

Additional context

No response

@cl445
Copy link

cl445 commented Jul 7, 2024

One possible solution is to define the network range that Docker uses to dynamically create networks. This range should be outside the one used by Mailcow to avoid conflicts. This can be achieved by adding the following lines to Docker’s daemon.json:

{
...
    "default-address-pools": [
        {
            "base": "172.23.0.0/16",
            "size": 24
        }
    ]
...
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants