Fortinet black logo

Administration Guide

Home FortiPresence 1.2.0 Administration Guide
1.2.0
1.2.0

Changing Default Subnet For Containers

Changing Default Subnet For Containers

Docker uses the default 172.17. 0.0/16 subnet for container networking. If this is already used in the network, perform the following steps to change the Docker subnet.

  1. Stop the Application services and the Infrastructure services.
  2. Login into the Infrastructure server (as root user) and edit the /etc/docker/daemon.json file to add the highlighted content.

    Note: Replace x.x.x.x/16 with the desired subnet range.
  3. Run the systemctl restart docker command to restart the Docker services.
  4. Repeat the previous steps on the Application server.
  5. [As presence user] Start the Infrastructure services before the Application services.
  6. Login into FortiPresence VM. If the dashboard data is not displayed, disable and enable the location services on FortiWLC or FortiGate.
Previous
Next

Changing Default Subnet For Containers

Docker uses the default 172.17. 0.0/16 subnet for container networking. If this is already used in the network, perform the following steps to change the Docker subnet.

  1. Stop the Application services and the Infrastructure services.
  2. Login into the Infrastructure server (as root user) and edit the /etc/docker/daemon.json file to add the highlighted content.

    Note: Replace x.x.x.x/16 with the desired subnet range.
  3. Run the systemctl restart docker command to restart the Docker services.
  4. Repeat the previous steps on the Application server.
  5. [As presence user] Start the Infrastructure services before the Application services.
  6. Login into FortiPresence VM. If the dashboard data is not displayed, disable and enable the location services on FortiWLC or FortiGate.
Previous
Next