Docker IP range

[subven]

No need to touch docker config. Just use the configuration menu for the mail server within Cloudron.

You may also take a look at the docs for additonal network/DNS configuration --> Link.

[savity]

@subven Did already i am forwarding everything to my internal DNS Server and the host can also get the IP over using Host MAILSERVERNAME.domain.
But i get directly the error the host is not reachable and as you can see on the Ping the route goes through the Docker IP-Bridge and there is no route i guess.

Since the Mail server is in the same network as Docker is.... this is the issue

[subven]

@savity aaaah so you really have to change the docker0 bridge network. Changing the daemon configuration should not be the problem but how to make it work persistent for Cloudron is something I can't answer right now.

Bye the way....it's not good practice and enterprisy to have your internal network at the default IP range for docker0 but I also saw bigger companys running 192.168.1.X internally....

[subven]

@savity hmm according to devs, it should be possible to change the network. Take a look at this post.

[savity]

@subven Trust me when i tell you..... i adressed this 1000 times

[subven]

@savity said in Docker IP range:

@subven Trust me when i tell you..... i adressed this 1000 times

Yeah gotya ^^ As system administrator I had to deal with users not beeing able to use VPN and stuff because of stupid networking design all the time. Companies grow and not all are able to fix their sins.

[savity]

@girish Would need help here i solved this issues by making configs directly on another Linux Machine by

/etc/docker/daemon.json
{
"default-address-pools":
[
{"base":"10.10.0.0/16","size":24}
]
}

[subven]

@savity said in Docker IP range:

@girish Would need help here i solved this issues by making configs directly on another Linux Machine by

/etc/docker/daemon.json
{
"default-address-pools":
[
{"base":"10.10.0.0/16","size":24}
]
}

Don't think this will work because from what I understand is that you have to recreate the containers. Take a look at the post I linked above.

[savity]

@subven I did and tried also with 10.10 network no chance still no route

[girish]

@savity said in Docker IP range:

is there a supported way to reconfigure the Docker IP range? So i can use my smtprelay witch is in the network 172.17

Cloudron uses the 172.18.x.x network for docker containers. So, I am guessing the problem is something else? The ping screenshot you posted in your initial post, is that from inside a container or is that from the host?

[savity]

@girish It is from the Host yes
I wanna Ping 172.17.x.x and this is the nic adapter IP
172.16.x.x/16

[savity]

@girish Then this must be the issue?
I did not creat those bridges and it is a standard cloudron installation

[girish]

@savity Ah indeed, it seems that docker uses 172.17 by default. Let me check how to workaround this.

[girish]

@savity OK, I might have a solution for this. Still testing. Hopefully, should have a workaround tomorrow.

[savity]

@girish Any news here girish.

[girish]

@savity So, create a file named /etc/systemd/system/docker.service.d/custom.conf:

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables --bip 192.168.1.1/24 

Then,

# systemctl daemon-reload
# systemctl restart box

If you do, docker network inspect bridge, you will see the IP has changed.