You need to signal-event nethserver-docker-update after config setprop portainer status enabled to make portainer available, I corrected my post again 
Then login to portainer and join the network there.
1 Like
OK, did it 
- Tried to do the last step:
Open Port 8000 by creating a service?
this is fantastic news. Finally removing the need and dependency of operating many servers, and different variations of servers.
A quick question on Docker.
Does it mean that any software on the internet that has support for docker and has docker install instructions can be installed on Nethserver using the Docker portainer module?
do they include ones with docker image too?
Create a service in cockpit:
Add name, port and access
This process opens port 8000 for red and green.
Maybe like this:
config setprop netbox status enabled TCPPort 8000 access green,red
config set netbox service status enabled
1 Like
Yes, this is the same process on command line.
These two lines should be enough:
config setprop netbox status enabled TCPPort 8000 access green,red
signal-event firewall-adjust
Yes. basically that should work. You need to check for port conflicts, some docker installations assume your local ports 80 and 443 are unused so you need to change ports for example.
Sorry, I don’t understand…
EDIT:
Yes, docker images are supported.
1 Like
would another mail software running inside docker on Nethserver that has nethserver-mail enabled produce conflict, or it will work just as fine.
In this case i am referring to something like mailcow.email | The mailserver suite with the ‘moo’ – 
+ 
= 
It’s a challenge because the default mailports are in use locally by nethserver-mail, so you need to use other ports or don’t use local dockerproxy port bindings at all and talk to the container directly (by using aeria or macvlan network)…
OK, sorry…
No problem. I used the reverse proxy way and I think shorewall still blocks access to port 8000…I need to check…
For quick testing you may disable shorewall firewall with
shorewall clear
and browse to
http://<nethserver>:8000
To reenable the firewall use
signal-event firewall-adjust
Did not work for me…
After a reboot netbox-docker_netbox_1 was stopped…
The Container runs in another Subnet as the Nethserver, I think this is OK by design?
After reboot you need another docker-compose up -d again to bring the containers up and you need to join the aqua network again.
Yes, that’s ok.
I recommend the reverse proxy way to not need to open non default ports.
Is it possible to automate this?
I did:
Can now connect to the Netbox-Container:
Thank you for your Help! 
1 Like
Yes, I think the start option can be set in portainer, this way the aqua network should be kept because we don’t need docker-compose anymore.