It's currently not possible to force updating a service's image, for example, if a service uses nginx:1.11.1-alpine, and an updated version is available for that tag, it's not possible to force pulling the latest version.
Related; when deploying a service, we want to be sure that each node uses the exact same version of the image.
We briefly discussed this yesterday, and are thinking of having Docker determine the sha256/digest of the specified image, and use that to deploy the service. When updating a service, the sha256/digest of the image is checked again, to know if an updated version is available and should be pulled.
/cc @mgoelzer @aluzzardi @tonistiigi @tiborvass
It's currently not possible to force updating a service's image, for example, if a service uses
nginx:1.11.1-alpine, and an updated version is available for that tag, it's not possible to force pulling the latest version.Related; when deploying a service, we want to be sure that each node uses the exact same version of the image.
We briefly discussed this yesterday, and are thinking of having Docker determine the sha256/digest of the specified image, and use that to deploy the service. When updating a service, the sha256/digest of the image is checked again, to know if an updated version is available and should be pulled.
/cc @mgoelzer @aluzzardi @tonistiigi @tiborvass