Hi there,
We’re using a third party image from docker hub for the source of one of our app platform components.
The third party releases bug fixes using the same tag, as in the 7.0 tag has recently been updated with version 7.0.9 with a new image and digest. Overwriting the old 7.0.8 version. The problem seems to be that whenever we update the app platform component it continues using the same version from when the component was first created.
So while our staging and production environments are both pointing to the same 7.0 tag, they’re actually running different versions of the container as staging was created long before production. Our staging component is running 7.0.2 while production is on 7.0.8.
I’ve tried forcing an update to use the most recent digest for the tag by updating the source tag to a different tag and back to 7.0 again as well as updating env vars to trigger a redeploy of the component. Each method failed as it seems like digital ocean has cached the old digest for that tag for the component meaning that each time we go back to 7.0 it carries on using the old version and doesn’t pull down the most recent digest for that tag.
What I was wondering about is if there is a way to clear the reference to the old digest for the component so when we redeploy the component it pulls down the most update to that tag please?
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
