You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the container already on other docker host with success.
For my new installation I simply copied the configuration and adapted the ip adresses.
While starting i get only this message:
AH00534: apache2: Configuration error: No MPM loaded.
I searched already and the reason shall be a missconfigured apache especially inside the http.conf.
Searching via find insinde docker host and inside container created from this image I could not find an http.conf file in order to check it.
Both docker hosts (the working and the not working) don't have any apache installation.
I tried to start the image completely without volume mounts and environment variables (bare image) and also got this exception.
Obviously the image is somehow relying on underlying docker host.
The docker host is an centos7 vm. The not working centos VM is derived from the same centos vm like the first. I compared docker and docker-compose versions. (same)
I have no ideas anymore.
Is this issue known and what could be a solution?
Thanks
Maik
The text was updated successfully, but these errors were encountered:
I used the container already on other docker host with success.
For my new installation I simply copied the configuration and adapted the ip adresses.
While starting i get only this message:
AH00534: apache2: Configuration error: No MPM loaded.
I searched already and the reason shall be a missconfigured apache especially inside the http.conf.
Searching via find insinde docker host and inside container created from this image I could not find an http.conf file in order to check it.
Both docker hosts (the working and the not working) don't have any apache installation.
I tried to start the image completely without volume mounts and environment variables (bare image) and also got this exception.
Obviously the image is somehow relying on underlying docker host.
The docker host is an centos7 vm. The not working centos VM is derived from the same centos vm like the first. I compared docker and docker-compose versions. (same)
I have no ideas anymore.
Is this issue known and what could be a solution?
Thanks
Maik
The text was updated successfully, but these errors were encountered: