Closed angelocordon closed 5 years ago
https://github.com/docker/compose/issues/1393
Some more discussion and workarounds.
Yeah, I like this comment here: https://github.com/docker/compose/issues/1393#issuecomment-100301533
From https://auth0.com/blog/ruby-on-rails-killer-workflow-with-docker-part-1/
The second volume masks the tmp folder in the host OS so that all other project folders are available for the container except the tmp. When you run docker-compose down, this tmp folder within the container is wiped out.
Marking as closed in favor of #24
In some instances, when starting the container back up after stopping, a log error pops up:
Running
docker-compose ps
to list container status returns:A quick and dirty solution is to remove the server.pid file in the above directory:
Also see: https://stackoverflow.com/questions/35022428/rails-server-is-still-running-in-a-new-opened-docker-container
However, logging this as an issue to keep track of how frequent this is happening and that we should look for ways around it so that restarting a container back up is more predictable.