No subnet declaration for docker0

UCS - Univention Corporate Server
,
#1

Hi@all,

A few days ago I installed a new UCS5 environment.

1 x Master
2 x Managed node

On one of the nodes I installed Nextcloud. Now I wanted to set that up. Unfortunately I found out that the Docker container is not running:

root@cloud01:~# univention-app shell nextcloud
Cannot run command: 4.4/nextcloud=21.0.7-0 is not running in a container

root@cloud01:~# docker container list
CONTAINER ID        IMAGE                                               COMMAND                  CREATED             STATUS              PORTS                    NAMES
f5f3f790f270        docker.software-univention.de/collabora:6.4.10.10   "/bin/sh -c 'bash st…"   6 days ago          Up 7 minutes        0.0.0.0:9980->9980/tcp   angry_payne

I don’t know if there is a connection but I found the following entries in the log on the master:

Feb 10 16:25:45 srv01 systemd[1]: Starting ISC DHCP Server for IPv4...
Feb 10 16:25:45 srv01 systemd[1]: Started ISC DHCP Server for IPv4.
Feb 10 16:25:45 srv01 dhcpd[5061]: Wrote 0 leases to leases file.
Feb 10 16:25:45 srv01 dhcpd[5061]: 
Feb 10 16:25:45 srv01 dhcpd[5061]: No subnet declaration for docker0 (172.17.42.1).
Feb 10 16:25:45 srv01 dhcpd[5061]: ** Ignoring requests on docker0.  If this is not what
Feb 10 16:25:45 srv01 dhcpd[5061]:    you want, please write a subnet declaration
Feb 10 16:25:45 srv01 dhcpd[5061]:    in your dhcpd.conf file for the network segment
Feb 10 16:25:45 srv01 dhcpd[5061]:    to which interface docker0 is attached. **
Feb 10 16:25:45 srv01 dhcpd[5061]: 
Feb 10 16:25:45 srv01 dhcpd[5061]: Server starting service.

Does anyone know this problem or better a solution?

with best
sven

#2

Hi,

please post:

docker images |grep --color nextcloud

and

univention-app info

Thank you.

#3 
root@cloud01:~# docker images |grep --color nextcloud
docker.software-univention.de/nextcloud   21.0.7-0            1c36271a798a        2 months ago        1.18GB
docker.software-univention.de/nextcloud   20.0.9-0            1e6e540ebbd7        10 months ago       1.11GB

root@cloud01:~# univention-app info
UCS: 5.0-1 errata218
Installed: 4.4/collabora=6.4.10.10
Upgradable:
#4

Thanks,

check this article to remove the

docker.software-univention.de/nextcloud   20.0.9-0            1e6e540ebbd7        10 months ago       1.11GB

and restart docker

systemctl restart docker

Than check again to get into the shell.

#5

Okay, now this is scary. Basically NextCloud was no longer shown as “installed” in the Appcenter :flushed:

I installed it again and now I get into the container. This was/is not tragic since nothing has been done on the VM yet.

However, the message on the master when I restart the DHCP remains:

I have found entries in the bug tracker but they do not provide a solution :frowning:

https://forge.univention.org/bugzilla/show_bug.cgi?id=39872

The only change I made to the DHCP is. Advanced options:

tftp-server-name "http://192.168.83.8:8880/p/gehr01/{mac}"

I need these for Pascom. I have removed the entry for testing. The message remains :frowning:

#6

Cool that the container is back again.

You are not alone with that… :sweat_smile:
So please check this first,

#7

I have read it but that does not describe my problem. My DHCP server is running. It only reports this error with the subnet for Docker

#8

I have another UCS5 test environment on the notebook in virtmanager. I have started this and tested it.

Dot this message is also issued in the log when the DHCP server is restarted.

This looks like a bug to me

#9

Ok but beside the log, what ist the problem ?

#10

I have not been able to detect any so far. From this point of view, there is no need to rush. I just don’t like red errors in the logfile and wanted to pass the information :slight_smile:

Mastodon