R
RunPod12mo ago
Chanchana

How to force Runpod to pull latest docker image?

I have built the docker image that runpod template relies on, and I want runpod to use the latest docker image i just built, how can i do it? I saw there is a button called New Release but it's asking me to use a new tag. I don't want to use a new tag. My docker image is using the same old tag.
9 Replies
flash-singh
flash-singh12mo ago
use newer tags and update template with new tag if you dont want to use tags, you can try hashes
Chanchana
ChanchanaOP12mo ago
quite inconvenient because i use the autobuilds feature of docker and it uses the same tag name every time it builds how can i do this? how does the path look like?
flash-singh
flash-singh12mo ago
ubuntu:18.04@sha256:98706f0f213dbd440021993a82d2f70451a73698315370ae8615cc468ac06624 try that
Chanchana
ChanchanaOP12mo ago
How would the full path look like? Or is that already a full path to set in Runpod? I don't see mentioning of user/repo
flash-singh
flash-singh12mo ago
thats full path runpod/worker@sha256:98706f0f213dbd440021993a82d2f70451a73698315370ae8615cc468ac06624
Chanchana
ChanchanaOP12mo ago
this seems to work. Thanks! I have another question: what about when modifying the template e.g. changing AWS user env var, would that force runpod worker to restart?
ashleyk
ashleyk12mo ago
You have to set workers to zero and back up again for changes to environment variables to take effect
Chanchana
ChanchanaOP12mo ago
thanks!
flash-singh
flash-singh12mo ago
we are planning a better release process that will be faster and detect env changes as well, eta in feb
Want results from more Discord servers?
Add your server