Nethserver-portainer needs testers AND ideas :D

(Stéphane de Labrusse) #81

Ideas will come later, for now : hourra

(Stéphane de Labrusse) #82
[root@ns7loc13 ~]# db configuration set docker service status enabled
[root@ns7loc13 ~]# signal-event nethserver-docker-update 

you missed something, docker is down after the installation

EDIT : too fast, missing to read the README, it is wanted

(Markus Neuberger) #83

I tested it on a VM (1 green interface) and on a gateway server (green and red)

On the gateway app templates are missing, I only got 8 templates. (usually there are more categories in the drop-down too):

I tried caddy and joomla but I always get to the Nethserver default page instead of the portainer apps when browsing to http://nethserver:portainerport.

Dedicated storage seems to work (docker volumes are created).

The portainer app button is missing.

After installation it worked but when I did signal-event nethserver-docker-update more often, it happened that portainer was not reachable.

(Stéphane de Labrusse) #84

Ok I can create a basic container (tried alpine and ubuntu) think to use the good setting in portainer ->interactive & tty

for the network, set an IP in the network range, I am not sure for the mac address it should work with the default one.

at least this what I missed first

(Davide Principi) #85

It can be a symptom of a lack of connectivity. I ran this experiment:

  • configured nethserver-docker on a green-only host
  • added red interface later
  • tried to ping from an alpine container
    wget -qO-

The ping was blocked. I found the aqua0 bridge was DOWN. It wasn’t bring up by interface-update event. So we need to add some logic to it, to bring it up again. This command was enough to work around the issue:

 ip link set aqua0 up

Please check the aqua0 state: if you find it DOWN take note of it!


just a quick test, and probably i miss something… i tested on a VM with only a green interface.
dedicated storage seems ok, but i cannot reach the exposed port of the container, any hints?

(Davide Principi) #87

Forgot the Docker facilities that automatically expose a TCP port by altering the packet filtering / nat configuration :blush: : they are disabled in NethServer!

You have to define a port forward in the NethServer firewall configuration manually.

Edit: If you want to expose a web site, configure the Reverse Proxy

For developers: I think this can be done automatically (and easily) by an RPM too…

(Davide Principi) #88

A post was split to a new topic: Help needed with firewall and nethserver-docker

(Kirk Macdonald) #89

For any one who is using the docker swarm and I repeat this is only for docker swarm

to install traefik reverse proxy

docker network create --driver=overlay traefik-net

this creates a new overlay network for traefik to work on

then we need to create the service

docker service create
–name traefik
–publish 80:80
–publish 8080:8080
–mount type=bind,source=/var/run/docker.sock,target=/var/run/docker.sock
–network traefik-net

then you can access it via local ip :8080

web where documentation for this