Container Stuck in 'restarting' state. (ServerName Error (fixed))

[ghost]

[Context: ADOP/C Instance running on a cloud server. Initially provisioned through the command line using ./adop compose init]

ldap-ltb container was stuck restarting, which in turn stopped ngnix from working.

Logs from ldap-ltb gave the following error:

> Could not reliably determine the server's fully qualified domain name, using 172.18.0.4. Set the 'ServerName' directive globally to suppress this message
> Could not reliably determine the server's fully qualified domain name, using 172.18.0.5. Set the 'ServerName' directive globally to suppress this message

and so on with various IP addresses.

A search lead to the following forums ( A and B ) which both suggested the solution to be adding the line ServerName localhost into the config files for Apache2.

To access ldap-ltb in order to edit it, we used the following command:

docker run -v /home/My home directory/ -it accenture/adop-ldap-ltb:latest /bin/bash

From here we found the necessary file and edited it using vi /etc/apache2/apache2.conf, adding the line ServerName localhost at the end of the file as advised by the forums.

With the change in place we went to the location in the server where the ADOP repo was cloned, and ran the command ./adop compose init --with-stdout to run the ADOP initialisation again in order to set up the ldap-ltb correctly.

After this the container started working again.

--

[Note: We also had to kill and restart the jenkins-slave container to make it work correctly, but unsure how related this was.]