Univention Bugzilla – Bug 44296
make systemd options in appcenter docker create optional
Last modified: 2020-07-03 20:56:33 CEST
The new systemd options --tmpfs /run --tmpfs /run/lock can cause problems for (official) images. e.g. A docker container does not use systemd, but starts apache directly in the entry-point. During the generation of the container apache lock dir /var/lock/apache2 is created and once the container is started this directory is used by apache. /var/lock is a link to /run/lock. But when the container is started with --tmpfs /run/lock --tmpfs /run docker mounts tmpfs onto these directories and the apache2 directory disappears. Now apache is unable to start AH00526: Syntax error on line 74 of /etc/apache2/apache2.conf: Invalid Mutex directory in argument file:/var/lock/apache2 -> docker run -e container=docker --tmpfs /run --tmpfs /run/lock wordpress:4.6.1 /usr/local/bin/apache2-foreground AH00526: Syntax error on line 74 of /etc/apache2/apache2.conf: Invalid Mutex directory in argument file:/var/lock/apache2 -> docker run -e container=docker wordpress:4.6.1 /usr/local/bin/apache2-foreground AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message [Wed Apr 05 12:53:36.266625 2017] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.10 (Debian) PHP/5.6.28 configured -- resuming normal operations [Wed Apr 05 12:53:36.266848 2017] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND' see also https://github.com/docker-library/php/issues/250 so we have to make these parameter optional (DisbaleSystemdOpts in ini file and if true remove the systemd option from the create command)
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.