Closed bscheshirwork closed 7 years ago
That's an Engine issue, not a Compose issue, as pointed out in #3241. Do you mind reporting it there instead? http://github.com/docker/docker
So... The docker-compose
set up starting config for Docker
engine... Any other actions (include restart containers after a system reboot) - is the Docker
engine responsibility. It is correct?
Yes, that is correct.
Like #3241 and #872 some composition don't (re)start correctly after reboot. docker-compose.yml (1)
In the
docker ps
list STATUS is "Up 5 minutes"docker inspect -f "{{ .HostConfig.RestartPolicy }}" <container>
returnalways
for all containerBut service does not work correctly http access to web server 0.0.0.0:8081 0.0.0.0:8082 0.0.0.0:8083 (Connection was dropped), connect to db 3307 (Some strange: I can connect, but I can see the information schema only) (php not tested)
Same situation with (2)
And other composition is running correctly at same time:
sameersbn/gitlab
The another composition for same config (env difference) may up correctly after reboot https://github.com/bscheshirwork/docker-yii2-app-advanced-rbac/blob/master/docker-compose.yml (3)
And if I up then together ( (2) and (3) ) - all of it is fails after reboot
After run docker-compose restart manually
services is run correctly
Any ideas?