ON THIS PAGE
Configure Apstra Docker Subnets
The Apstra server Docker containers require one network for internal connectivity, which is automatically configured with the following subnets:
- docker0: inet 172.17.0.1/16
- Apstra same VM (in-place) upgrade docker network: inet 172.18.0.1/16
If you need to use these subnets elsewhere, to avoid conflicts, change the Docker network as follows:
docker0
Update bip
with the new subnet. If the
/etc/docker/daemon.json
file doesn't already exist, create one
with the following format (Replace 172.26.0.1/16
in the example
below with your own subnet.):
$ sudo vi /etc/docker/daemon.json { "bip": "172.26.0.1/16" } $ sudo service docker restart $ sudo service aos restart
Docker Network and Apstra Upgrades
If you're upgrading your Apstra server on the same VM that's it currently on, the Apstra upgrade creates an additional Docker network. By default in Docker, this network is 172.18.0.1/16. If you're using this subnet elsewhere on your network, the Apstra upgrade could fail.
To use a different subnet, create or edit the
/etc/docker/daemon.json
file with the following format (Replace
172.27.0.0/16 in the example with your own subnet).
$ sudo vi /etc/docker/daemon.json { "default-address-pools": [ { "base": "172.27.0.0/16", "size": 24 } ] } $ sudo service docker restart $ sudo service aos restart