WIFIonICE vs Docker: Fixing DB (Deutsche Bahn) WIFI by moving Docker away from 172.18.x.x in /etc/docker/daemon.json

etc-docker-daemon.json

{
    "bip": "172.39.1.5/24",
    "fixed-cidr": "172.39.1.0/25",
    "runtimes": {
        "nvidia": {
            "path": "nvidia-container-runtime",
            "runtimeArgs": []
        }
    }
}

With the above solution, each time when connecting to WIFIonICE I was forced to remove networks created by docker compose again – which invalidated images and lead to running docker prune way too often…

This works for a couple of months now, without the need to prune networks each time (only once after initial setup):

/etc/docker/daemon.json

{
    "bip": "172.39.1.5/24",
    "fixed-cidr": "172.39.1.0/25",
    "default-address-pools":
    [{
        "base": "172.39.0.0/16",
        "size": 24
    }],
    "runtimes": {
        "nvidia": {
            "path": "nvidia-container-runtime",
            "runtimeArgs": []
        }
    }
}

Doesn't work for me =(

The address for docker0 complies, but the br-<somethin> networks continue to use the 172.18.x.x range

Docker version 23.0.4, build f480fb1

Edit:

Ok, just got it working by running docker network prune. Networks created after that will use the new range

Nice! 🚀

I had to delete all already existing container and images. After i did that, it worked.