You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Watchtower updates the container by pulling the new image and recreate a new container of the new image. But the new container runs with the old healthcheck arguments instead of the updated ones:
If you manually re-create the container, e. g. using docker-compose pull and docker-compose up -d, the updated health check parameters will be applied to the new container:
Interesting! Yeah, I think we copy the current container spec to the teeth, including any healthcheck declarations that it might have. Will have to look into how to honor changes to it.
Describe the bug
An image specifies the health check with various arguments, e. g. the following health check:
container: (
$> docker inspect kjn2kj3498
)The image author updates the health check parameters, e. g. timeout will be increased to 15s, and retries to 4:
Watchtower updates the container by pulling the new image and recreate a new container of the new image. But the new container runs with the old healthcheck arguments instead of the updated ones:
$> docker inspect ui43j3na
If you manually re-create the container, e. g. using
docker-compose pull
anddocker-compose up -d
, the updated health check parameters will be applied to the new container:$> docker inspect asdn2904ds
Steps to reproduce
docker build --no-cache -t healthcheck-image .
docker push healthcheck-image
timeout
andretries
ParameterExpected:
Do the same with
docker-compose up -d --force-recreate
. The expected healthcheck configuration will be applied.Expected behavior
The container should be recreated with the updated healtcheck configuration
Screenshots
No response
Environment
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: