Repository navigation
Replies: 1 comment
|
This is almost always Docker's image cache docker compose up won't re pull a tag that already exists locally, even if :latest on the registry has moved. Try one of these: Force a pull, then recreateOr
If the above doesn't workTo confirm you're actually on the new image, check the digest: |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have this as my image in the docker compose file: services: image: ghcr.io/alam00000/bentopdf:latest # Recommended
But for some reason I'm still all the way back on version 1.15.3. Even though docker says it's pulling the latest. Doing something wrong?
All reactions