Php: SIGWINCH issue

Created on 21 Jan 2015  路  10Comments  路  Source: docker-library/php

When making a derived image from php:5.6-apache, when the server starts, at the slightest movement it stops, and gives me this message:

[Wed Jan 21 20:24:05.736731 2015] [mpm_prefork:notice] [pid 1] AH00170: caught SIGWINCH, shutting down gracefully

It happens when I resize the window, or on docker attach, rendering it inaccessible.

Most helpful comment

I found the solution to my problem, I run docker exec -it container-name bash

All 10 comments

Can you try running without "-t" and see if the problem persists?

The command issued is apache2 -D FOREGROUND. No -t argument.

I mean on your docker run.

Nope. The original command issued is:

docker run -it --rm --name test_server -p 8181:80 test-example

And now I replaced it with:

docker run -i --rm --name test_server -p 8181:80 test-example

Looks like more of an Apache issue.

I received the same error on my first run, but things went fine in the second run.

Apache is working as-designed according to a bug report.

Running docker run with --sig-proxy=false prevents SIGWINCH (and all other signals) from being sent to apache.

Please at least change the recommended command line options on Docker Hub.

I have the same issue with docker-compose, so I can't running docker run with --sig-proxy=false.
When I use --sig-proxy with docker attach it does not change anything.
How can I resolve this issue ?

I found the solution to my problem, I run docker exec -it container-name bash

If is start it with --sig-proxy=false then ctrl + c is ignored, --detach is also a non-solution 1. --rm doesn't work with -d 2. i want it to run attached

Was this page helpful?
0 / 5 - 0 ratings

Related issues

skyzyx picture skyzyx  路  3Comments

solocommand picture solocommand  路  3Comments

2Kable picture 2Kable  路  3Comments

cordoval picture cordoval  路  3Comments

ktrzos picture ktrzos  路  3Comments