Hi Juan Carlos,

After a Docker installationis finished, the Bridge interface docker0 is created by default and it's IP range is 172.17.0.0/16. But you can create another network interfaces running docker network create new_network_name

If you want to change the docker0 settings, you can use the daemon.json file in /etc/docker/

If the file is not their you can create it and specify some parameters like the following for the bridge network:

{

"bip": "10.10.10.5/24",

"fixed-cidr": "10.10.10.5/25",

"fixed-cidr-v6": "2001:db8::/64",

"mtu": 1500,

"default-gateway": "10.20.1.1",

"default-gateway-v6": "2001:db8:abcd::89",

"dns": ["10.20.1.2","10.20.1.3"]

}

Then restart Docker. Hope this can help you.

Best Regards,

Javier Romero

El mié., 6 feb. 2019 a las 14:21, Alonso, Juan Carlos (<juan.carlos.alonso@intel.com>) escribió:

Hi,

For today’s ISO, in Simplex and Duplex configurations, we noticed a new interface called ‘docker0’, our framework takes the first interface and set a temporary ip address, but this ‘docker0’ interface could not be set, then STX setup fails.

We applied a workaround to take the next interface to continue the STX tests.

We also noticed that this ‘docker0’ interface is not present in Multinode configurations.

localhost:~$ ls /sys/class/net

docker0 enp2s1 enp2s2 eth1000 eth1001 lo

Is this new interface enabled for configuration with kubernetes? Will this interface be enabled in Multinode configurations?

Why docker0 interface cannot be set with an ip address?

Regards.

Juan Carlos Alonso

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss