beast icon indicating copy to clipboard operation
beast copied to clipboard

AutoHealing docker challenge containers.

Open fristonio opened this issue 6 years ago • 2 comments

If a container is removed or stopped, we should automatically start the container and also show the user the restart count.

fristonio avatar Jan 14 '19 07:01 fristonio

Can this be linked to the healthprober or a different containerprobe is required for healing @fristonio

kokil87 avatar Jun 18 '19 06:06 kokil87

This is not essentially a container probe. I think we create a new function in cr to start and restart a container and use that when we are not able to reach the container. Some things to keep in mind, we should only do restart for container which are only in deployed state and had a failed probe attempt for more than 5 times.

One more improvement I see here is if we create a map for health probes in health_check which will contain all this metadata related to probes. This is because we might see a false probe fail if the probe is executed while the container is executing post-build.sh file.

fristonio avatar Jun 18 '19 07:06 fristonio