It should be possible to change the container's Network Configuration via GUI. I guess its enough to provide either NAT or Bridged mode:
Hidden (NAT)
In this mode each container operates in its own network. It's connection to the outside world is done using network address translation (NAT).
Pros
as the hosts network configuration is used to access the outside world, there is no need for the user to configure anything. It just works out of the box.
Cons
It is not easily possible to connect to the container from the host system or other containers.
Visible (Bridged)
In this mode the network connection of the container is bridged into the local area network (LAN). Therefore the container appears as a regular computer within the local network.
Pros
The host system as well as any other computer in the network can easily connect to the container (as long as the firewall configuration permits the access).
Cons
There is no way to be sure the container receives a valid network configuration automatically. So the user must decide whether or not they want to use DHCP and if not, provide a valid static network configuration.
It should be possible to change the container's Network Configuration via GUI. I guess its enough to provide either NAT or Bridged mode:
Hidden (NAT)
In this mode each container operates in its own network. It's connection to the outside world is done using network address translation (NAT).
Pros
Cons
Visible (Bridged)
In this mode the network connection of the container is bridged into the local area network (LAN). Therefore the container appears as a regular computer within the local network.
Pros
Cons