Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
external-header-nav
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configure Apstra Docker Subnets

date_range 03-Sep-24

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.):

content_copy zoom_out_map
$ 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

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).

content_copy zoom_out_map
$ 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
external-footer-nav