Having broken my littlelink container trying to get it to upgrade I started again again from scratch with a new container, pull and new volume ... determined to make this work!!
Latest pull using v3.0.3 image sha256:6ce23bffd4cd5b17dcdfb09cdc7943ff4c75637da2c882f0671ac0cada82c111
I found the same issue that I saw before with the following messages appearing after a docker instance is stopped and restarted.
Updating Configuration: Apache Base (/etc/apache2/httpd.conf)
Updating Configuration: Apache SSL (/etc/apache2/conf.d/ssl.conf)
Updating Configuration: PHP (/etc/php8/php.ini)
Updating Configuration: Complete
Running Apache
AH00526: Syntax error on line 337 of /etc/apache2/httpd.conf:
Invalid command 'io', perhaps misspelled or defined by a module not included in the server configuration
Before restarting I extracted the HTTPD.CONF as I was expecting the problem and it looked like this at the offending location
BrowserMatchNoCase ^healthcheck nolog
CustomLog "logs/access.log" combinedio env=!nolog
</IfModule>
I then dumped the container as it was not running/runable and I had no persistent storage for /etc/apache2 setup to extract the httpd.conf file
BrowserMatchNoCase ^healthcheck nolog
BrowserMatchNoCase ^healthcheck nolog
CustomLog "logs/access.log" combinedio env=!nolog
io env=!nolog
</IfModule>
I also ran a diff and these were the only differences!! (All empty lines stripped out from the above extracts)
Note that if I try to restart the httpd.conf is modified again and this time
BrowserMatchNoCase ^healthcheck nolog
BrowserMatchNoCase ^healthcheck nolog
BrowserMatchNoCase ^healthcheck nolog
CustomLog "logs/access.log" combinedio env=!nolog
io env=!nolog
io env=!nolog
</IfModule>
Having broken my littlelink container trying to get it to upgrade I started again again from scratch with a new container, pull and new volume ... determined to make this work!!
Latest pull using v3.0.3 image sha256:6ce23bffd4cd5b17dcdfb09cdc7943ff4c75637da2c882f0671ac0cada82c111
I found the same issue that I saw before with the following messages appearing after a docker instance is stopped and restarted.
Before restarting I extracted the HTTPD.CONF as I was expecting the problem and it looked like this at the offending location
I then dumped the container as it was not running/runable and I had no persistent storage for /etc/apache2 setup to extract the httpd.conf file
I also ran a diff and these were the only differences!! (All empty lines stripped out from the above extracts)
Note that if I try to restart the httpd.conf is modified again and this time