Question

My App is running old images after a successful deployment

Posted November 30, 2021 170 views
Node.jsDockerBuilding on DigitalOcean

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?

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.

×
Submit an Answer
1 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?

Nate

  • Thanks for the reply! I didn’t even realize the “Force Rebuild and Deploy” option was there, but this did resolve the problem.

    Obviously it’d be better if cached images weren’t used when a newer image is available, but at least this is a workaround!