Relution does not start after install

Hello,
I am running UCS 4.4-2 and tried to install Relution on the UCS Master from the App Center. The install script did not report any obvious error to me but relution is not starting.

With docker ps -a I found the relution container exited. Checking the log of the container with docker logs <container_id> I got the following log:

ERROR 2005 (HY000): Unknown MySQL server host 'ucs-server.myorg.local' (-2)

Since I really run it with a domain that does not publically resolve I inspected the container a little bit more regarding DNS.
The resolv.conf file docker generated for the container looks like this:

type or paste code here# Warning: This file is auto-generated and might be overwritten by
#          univention-config-registry.
#          Please edit the following file(s) instead:
# Warnung: Diese Datei wurde automatisch generiert und kann durch
#          univention-config-registry ueberschrieben werden.
#          Bitte bearbeiten Sie an Stelle dessen die folgende(n) Datei(en):
# 
# 	/etc/univention/templates/files/etc/resolv.conf
# 


domain	myorg.local
options timeout:2

nameserver 8.8.8.8
nameserver 8.8.4.4

I “assume” that Google DNS does not know about my local domain.
So, how can I change the file to ask the UCS Master?
The file contains a header from Univention but the Relution container is built on CentOS.

Any hints would help.
BR,
Jörn

Hello @jolentes,

you probably ran into this issue, regarding the Docker network: https://forge.univention.org/bugzilla/show_bug.cgi?id=50295. The fix is going to be released the next days.

Have you been upgrading from UCS 4.4-1 or have you made a fresh installation of UCS 4.4-2? If latter is the case, you may also have been running into this: https://www.univention.com/blog-en/2019/10/technical-difficulties-with-ucs-4-4-2-download-image/

If you started off a fresh UCS 4.4-2 installation with the old image (downloaded before 2nd October), please download the latest image and use that one.

Best regards,
Nico

Hello @gulden,
it was an upgrade. I am going to wait for the fix.
BR,
Jörn

Hello @jolentes,

the fix has been released last week with Errata Update 300.

Best regards,
Nico