Issue running Docker

Support
1

NethServer Version: 7.9.2009
Module: docker

I’m following Docker — NethServer 7 Final to install docker and portainer but I’m rinning into some errors:

failed to start daemon: error initializing graphdriver: /dev/sdb is not available for use with devicemapper

When I looked into it I saw that this error makes sense because when i do a “df -h” it doesn’t show /dev/sdb existing.

So I deleted the prop that led up to this with “config setprop docker DirectLvmDevice /dev/sdb” and did a docker-update (signal-event nethserver-docker-update) but now it shows:

 failed to start daemon: error initializing graphdriver: /var/lib/docker contains several valid graphdrivers: devicemapper, overlay2; Please cleanup or explicitly choose storage driver (-s <DRIVER>)

How can I get this working?

2

Please show

config show docker
config show portainer

3

Docker config:

docker=service
DirectLvmDevice=
IpAddress=172.28.0.1
Network=172.28.0.0/16
bridgeAeria=
enableRepository=disabled
macVlanGateway=
macVlanLocalNetwork=
macVlanNetwork=
macVlanNic=
status=enabled

Portainer config:

portainer=configuration
status=enabled

[edit] I’ve disabled the LvmDevice because that was the source of my first error

4

I could reproduce the issue.

I was able to reset it by removing the devicemapper:

rm -rf /var/lib/docker/devicemapper

Now apply the config, it fails the first time but the second run works:

signal-event nethserver-docker-update

Docker should now work again.

1 Like
5

Looks like docker is working, but portainer isn’t.
When I go to https://<ip>:9090/portainer/ I just get a not found error.
The console output from the first try of your command is:

-- Logs begin at Mon 2021-11-29 19:00:42 UTC. --
Nov 29 19:02:37 nethserver.pieterhouwen.info dockerd[5022]: time="2021-11- 
29T19:02:37.825577669Z" level=info msg="IPv6 enabled; Adding default IPv6 external servers: 
[nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844]"
Nov 29 19:02:37 nethserver.pieterhouwen.info containerd[1089]: time="2021-11- 
29T19:02:37.850516403Z" level=info msg="shim containerd-shim started" address="/containerd- 
shim/moby/88caa94c1894db779fe7f05a7a84a1d6fe6ea64fd225d3210d690f4c88075d53/shim.sock"  debug=false pid=5954
Nov 29 19:02:38 nethserver.pieterhouwen.info kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 29 19:02:38 nethserver.pieterhouwen.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE): 
eth0: link becomes ready
Nov 29 19:02:38 nethserver.pieterhouwen.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE):     veth251ab5e: link becomes ready   
Nov 29 19:02:38 nethserver.pieterhouwen.info kernel: aqua0: port 1(veth251ab5e) entered blocking state
Nov 29 19:02:38 nethserver.pieterhouwen.info kernel: aqua0: port 1(veth251ab5e) entered forwarding state
Nov 29 19:02:38 nethserver.pieterhouwen.info kernel: IPv6: ADDRCONF(NETDEV_CHANGE): aqua0: link becomes ready
Nov 29 19:02:38 nethserver.pieterhouwen.info esmith::event[4686]: Action: /etc/e-smith/events/nethserver-docker-update/S95nethserver-docker-create-portainer SUCCESS [14.007579]
Nov 29 19:02:38 nethserver.pieterhouwen.info esmith::event[4686]: Event: nethserver-docker-update SUCCESS

I don’t see console output when I try the portainer url

6

The correct port is 980, like https://<ip>:980/portainer/

Let’s check if portainer is running:

docker ps -a

1 Like
8

Thank you! Just using the other port number was enough to show portainer interface!

2 Likes