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
Bug description
Re-creating (or editing) a container won't update healthchecks if they specification changes inside the image specification.
Expected behavior
On container re-creating/edit, health checks settings (such as commands, interval, etc) are updated if they're updated in the container image.
Steps to reproduce the issue:
Create a container image with an healthcheck (type CMD-SHELL)
Run a container from that image
Update the image, changing healthchecks parameters (I tried changing CMD-SHELL in CMD)
Re-create (or edit) the container. The new container will use old configurations for healthchecks.
Technical details:
Portainer version: 1.22.1
Docker version (managed by Portainer): 19.03.1
Platform (windows/linux): Debian Linux 9
Command used to start Portainer: docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
Browser: Firefox
Additional context
Healthchecks are created correctly if no healthchecks were specified in the previous image definition.
The text was updated successfully, but these errors were encountered:
Bug description
Re-creating (or editing) a container won't update healthchecks if they specification changes inside the image specification.
Expected behavior
On container re-creating/edit, health checks settings (such as commands, interval, etc) are updated if they're updated in the container image.
Steps to reproduce the issue:
CMD-SHELL
)CMD-SHELL
inCMD
)Technical details:
docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
Additional context
Healthchecks are created correctly if no healthchecks were specified in the previous image definition.
The text was updated successfully, but these errors were encountered: