-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container won't start twice: "httpd (pid 13) already running" #187
Comments
https://github.com/docker-library/php/blob/bdfd0fc1d19102cd6f951614072a51eabf7191bf/5.6/apache/apache2-foreground
should already be doing this -- have you done a "docker-compose pull" to
make sure you've got the latest image?
|
I'm running into this issue on the |
Can you please try again with |
If they're not supported can we mention this on the readme / docker page? |
The description includes a section of "Supported tags" right at the top. 😉
|
Oh I see, it's |
Correct, but "5.6-apache" will track the latest PHP 5.6 release without you
having to update at each point release to stay supported (until the EOL of
PHP 5.6).
|
seterrychen
added a commit
to seterrychen/apt-mirror-http-server
that referenced
this issue
Jul 27, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Thanks for setting up this image. It's saving me a ton of time 👍
It seems like if you run
php:5.6-apache
through Docker Compose, it will run fine the first time, but not the second time, because it seems to be keeping a reference to the previous process ID.This have discussed here previously (in 2014): https://groups.google.com/forum/#!topic/docker-user/2dP09wrq5Qk
Is there any specific reason for this? Would you be OK with a PR that removes the left over PID before exiting, as shown in the link above.
Best regards,
Conrad
The text was updated successfully, but these errors were encountered: