My App is running old images after a successful deployment

I triggered a new deployment by pushing to my master branch in github. The build logs show my Docker images are built correctly, not caching any layers that shouldn’t be cached. The activity timeline shows the deployment was successful and live.

However, my running service doesn’t reflect the changes I made, and the date on the compiled JavaScript file in the running container for my Node.js app shows it was created yesterday.

How do I ensure that my app consumes new images as they are created?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

DigitalOcean Employee
DigitalOcean Employee badge
November 30, 2021
Accepted Answer

Hey there!

It sounds like this may be pulling a cached image. If you force a rebuild using the force rebuild option of this app are you seeing the new files pulled in?


Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel