Network Docker Container Range

Important

When troubleshooting network issues, verify that the address range is not in use.

If it is in use, use the following command to modify the Private Address Space, as described below: network container range add <private IP>

RFC-1918 states that the following three blocks of the IP address space are reserved for private internets:

10.0.0.0        -   10.255.255.255  (10/8 prefix)
172.16.0.0      -   172.31.255.255  (172.16/12 prefix)
192.168.0.0     -   192.168.255.255 (192.168/16 prefix)

This subnet block address range can be modified to another Private Address Space if needed.

View the current Private Address Space

Use the following command to display the current Private Address Space: network container range list

For example:

$ network container range list
    range: 10.1.2.1/24

Modify the Private Address Space

Use the following command to modify the Private Address Space: network container range add <private IP>

Important

A valid Private Address IP is required as input.

The range /24 is appended to the IP. For example, if 192.168.0.6 is used, the Private Address range 192.168.0.0/24 is used.

In a clustered environment, you could use the following command: cluster run all network container range add <private IP>

Setting a different Private Address Space on each node

If required, you can set the Private Address Space to be different on each node by running the add command on each individual node. For example:

$ network container range add 192.168.2.3
You are about to restart all services. Do you wish to continue?y
Application processes stopped.  (note this line changes dynamically)

Reconfiguring applications....
Application  processes started. (note this line changes dynamically)