Efficient serverless release with image caching
My current deploy system is to push a updated docker image to docker hub (with git hash as tag) and run "new release" and pass the updates docker hub instance tag. However, it does a full download of the new image (20-30gb) instead of caching. Every small update is currently very slow to roll out. Is there a more efficient way of doing deploys? Or letting it know that a docker image has been updated-in place during dev? Thank you!
5 Replies
Unknown User•11mo ago
Message Not Public
Sign In & Join Server To View
Yes the change is in the final layer.
Hmm that's a bummer since it makes deployment super slow
Unknown User•11mo ago
Message Not Public
Sign In & Join Server To View
can you pm me endpoint id
its the holidays, ill get to it next week, need to dig deeper to see if this is a bug, currently the system updates workers in place and uses whatever cache is on the server
@nerdylive @flash-singh thanks for getting back! I'll share more after the holidays, cheers