QNAP Containerstation: SIGWINCH kills Apache about baikal-docker

[ckulka]

Hi @kuerbis42 , I for some reason missed this... surely because of million of other PRs and issues in this repo.

I don't have a QNAP NAS so it's hard for me to reproduce, do you know which command is used to retrieve the container status?
I've found a few similar issues in httpd and php repos, so I'd like to see if the resolutions are similar or if there's something we can do with this image.

[kuerbis42]

Hi @ckulka, I missed this, too ;-)
If you want, I would set it up again, but know I ran baikal on my "big" apache2 server - there it works fine.
Greeting, kuerbis42

[ckulka]

Sorry for the delay - looking at docker-library/httpd#9, there's no good way to address it in the image, but to change how the container is run, i.e. running the container with the daemon flag -d.

I've checked if customising the start script or apache2-foreground could help, e.g. running it in the background and tailing the logs files, but it unfortunately didn't work out well enough - the SIGWINCH commands still get passed and Apache httpd terminates.

For now, I'll have to wait if there's a better solution from the httpd issue above, otherwise there's little I can do in this image.

As an alternative, I'd recommend the nginx variant, which not only doesn't have this issue, but also needs less resources.