May-22nd-2019, 12:11 PM
Hello Andreas,
the point is that the "cifx0" LAN interface is a construct made within the container only. All settings concerning ip addresses and routing remain in the container only in case bridge mode used. So imagine you have a set of 100 containers ... and all containers want to adjust the IP settings ... can't imagine what would happen. So this is why Docker is encapsulating and separating those network settings.
In case of Host mode the behaviour is different. The containers LAN respectively TCP/IP stack is shared with the one of the Host. So all your container settings will have immediate effect on the software running outside the container.
The conclusing is that netPI gets internet access via eth0 or wlan0 only, via "cifX0" only in Host mode. But why don't you want to run the container in Host mode?
Armin
the point is that the "cifx0" LAN interface is a construct made within the container only. All settings concerning ip addresses and routing remain in the container only in case bridge mode used. So imagine you have a set of 100 containers ... and all containers want to adjust the IP settings ... can't imagine what would happen. So this is why Docker is encapsulating and separating those network settings.
In case of Host mode the behaviour is different. The containers LAN respectively TCP/IP stack is shared with the one of the Host. So all your container settings will have immediate effect on the software running outside the container.
The conclusing is that netPI gets internet access via eth0 or wlan0 only, via "cifX0" only in Host mode. But why don't you want to run the container in Host mode?
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
