Compose: Restarting Unhealthy Containers

Created on 24 Apr 2019 · 5Comments · Source: docker/compose

There was this one about 2 years ago on that topic https://github.com/docker/compose/issues/4826

It looks like Docker Compose is pointing to Docker and Docker is pointing to orchestration tools.

Is it possible to have restart policy to depend on health status? It looks like the job for Docker Compose for me.

Also, it was there for version 2 compose files in depends_on section.

stale

Source

lig

👍21

Most helpful comment

Please open again as it is still relevant

InsOpDe on 13 Dec 2019

👍15

All 5 comments

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] on 21 Oct 2019

This issue has been automatically closed because it had not recent activity during the stale period.

stale[bot] on 28 Oct 2019

Please open again as it is still relevant

InsOpDe on 13 Dec 2019

👍15

When it will be able to?

pbelskiy on 16 Mar 2020

Imho there is no way to do this in compose, because compose is not running during runtime of a container or services (except you omit -d on up).
To monitor the health state of a container and do actions on change you need to have a daemon.
Implementing those actions into docker daemon looks much smarter to me.
moby/moby#28400