nethserver-docker

This is a prototype that integrates Docker based applications within NethServer.

• It defines a new firewall zone and docker network, aqua. Basically, containers are attached to aqua and they can talk each other. IP traffic from other zones, like green and red must be configured with the usual Firewall rules and Port forwarding pages
• As example to test integration with system services, connections from the aqua zone are allowed to the MySQL/MariaDB port 3306.

More port rules can be opened to the system services with a esmith db command:

db dockrules set customName aqua TCPPorts 12,23,56,89 UDPPorts 120,230,560,890 status enabled
signal-event firewall-adjust

• It exposes portainer dashboards through the httpd-admin Apache instance as https://<IP>:980/portainer/

The default Docker bridged network is enabled

Installation

Install the nethserver-docker package from nethforge-testing

yum install --enablerepo=nethforge-testing nethserver-docker

Configuration

If you have a free block device (required for production environments) assign it to Docker before starting it for the first time

config setprop docker DirectLvmDevice /dev/sdb

Review the current settings with

config show docker

• Network, is the IP network address of the aqua zone
• IpAddress, is the IP address of the Docker host in the Network above

Enable the docker service and start it for the first time

config setprop docker status enabled
signal-event nethserver-docker-update

Web user interface

Portainer is an interface to manage all containers running on this host or eventually on remote hosts, a property must be enabled before to create the portainer container:

config setprop portainer status enabled
signal-event nethserver-docker-update

Access the Portainer user interface at

https://<IP>:980/portainer/

The first time it is accessed, it asks to generate the administrative credentials.

Docker repository

The official repository of docker is bundled but not enabled, the upgrade might break the running containers. It is advised to stop all containers before to upgrade docker-ce.

To upgrade to the latest stable version of docker:

yum update --enablerepo=docker-ce-stable

to enable it permanently:

config setprop docker enableRepository enabled signal-event nethserver-docker-update

Open Firewall For testing purpose

For testing purposes you can open the docker network by policy. In a production environment you should leave this step and set firewall rules

mkdir -p /etc/e-smith/templates-custom/etc/shorewall/policy
cp /etc/e-smith/templates/etc/shorewall/policy/35aqua /etc/e-smith/templates-custom/etc/shorewall/policy/
cat << 'EOF' > /etc/e-smith/templates-custom/etc/shorewall/policy/35aqua
#
# 35aqua -- the Docker network policy
#
aqua net ACCEPT
$FW aqua ACCEPT
aqua $FW ACCEPT
loc aqua ACCEPT
EOF
signal-event firewall-adjust

Aeria network

NethServer docker provides a docker network named Aeria that is bound to a bridge. For bridge creation the server manager could be used. The same bridge cannot be shared among aeria and macvlan, it is a docker limitation.

To enable the Aeria network the bridgeAeria db prop has to be set to the name of the bridge

config setprop docker bridgeAeria br0
signal-event nethserver-docker-update

The NethServer DHCP module can be used to set IP addresses for the docker containers. By default docker containers use random MAC addresses so fixed ones need to be set for the containers to make DHCP reservations work.

Here is an example for starting pihole in the Aeria network and set the MAC address

docker run -d --name pihole -e TZ="Europe/Vienna" -e WEBPASSWORD="admin" -v "$(pwd)/etc-pihole/:/etc/pihole/" -v "$(pwd)/etc-dnsmasq.d/:/etc/dnsmasq.d/" --cap-add NET_ADMIN --net=aeria --mac-address=0e:6f:47:f7:26:1a --restart=unless-stopped pihole/pihole:latest

Aeria uses a docker plugin. To update the plugin

signal-event nethserver-docker-plugin-update

The aeria network is not standard on docker, the developer can be contacted at https://github.com/devplayer0/docker-net-dhcp

Debug:

After a docker update the plugin net-dhcp might be disabled

to check it : docker plugin ls to enable it : docker plugin enable devplayer0/net-dhcp

Macvlan

A container use TCP/UDP ports to communicate outside of the server, this is the default networking. However your container could need to get a real IP on your network. Like this it will be reachable with http://IPofYourContainer instead of http://IPofYourServer:port. A specific configuration like a DNS sinkhole (as pihole) must have an IP, because it might break the DNS resolution of your server. Therefore with a different IP, all hosts of your network will use the services of pihole like if it was on another server.

The difference between macvlan and aeria is that macvlan is not a plugin, it is an official network driver.

NethServer docker provides a docker network named macvlan that must be bound to a bridge. Each container on the network macvlan must have a relevant IP in the range assigned to macvlan, all containers will communicate like any servers on your network.

For the bridge creation the server manager could be used, if you have already installed the account provider Samba AD (nethserver-dc), you have already a bridge called br0. The same bridge cannot be shared among aeria and macvlan, it is a docker limitation.

A bridge is mandatory to macvlan, you must accomplish this step before to go further: ip a can valid that the bridge is up and workable

Macvlan must be created by filling some important parameters, the goal is to create a container with an IP on your network, each parameter depends from your network setting.

• macVlanGateway : It is the gateway of your network, generally speaking it is your router (here 192.168.1.1)
• macVlanLocalNetwork : It is the full network of your router (here 192.168.1.0/24 from 192.168.1.1 to 192.168.1.255)
• macVlanNetwork : It is the restricted IP for macVlan0 (here 192.168.1.224/27, you can use 30 IP for your containers from 192.168.1.225 to 192.168.1.254)
• macVlanNic : It is the network interface where to run macvlan (br0 here)

Create the network

config setprop docker macVlanGateway 192.168.1.1 macVlanLocalNetwork 192.168.1.0/24 macVlanNetwork 192.168.1.224/27 macVlanNic br0

Then trigger the event

signal-event nethserver-docker-update

You have to specify to use the network macvlan for your container, the default docker0 is another network.

Docker creation example on macvlan

docker run --net=macvlan -dit --name nginx-test-02 --ip=192.168.1.225 --restart=unless-stopped nginx:alpine nginx-debug -g 'daemon off;'

The container can be contacted at the relevant IP

curl http://192.168.1.225

In case of the proposed CIDR doesn't fit your need, you should have a look to an IP calculator : https://www.calculator.net/ip-subnet-calculator.html