41–50 of 110 posts
What's the easiest way to cache registries like docker, pypi, and npm these days?
explains why my watchtower container was exploding
Was already struggling to do any work today and now my builds aren't working. https://xkcd.com/303/
What would be really nice is a system with mutating admission webhooks for pods which kicks off a job to mirror the image to a local registry and then replaces the image reference with the mirrored location.
What's the easiest way to cache registries like docker, pypi, and npm these days?
You pull the images you want to use, preferably with some automated process, then push them to your own repo. And anyways use your own repo when pulling for dev/production. It saves you from images disappearing as well.
Was already struggling to do any work today and now my builds aren't working. https://xkcd.com/303/
for example, i have redis:7.2-alpine in cache, but not golang:1.24.5-alpine
I needed the golang image to start my dev-backend
so i replaced FROM golang:1.24.5-alpine with FROM redis:7.2-alpine, and manually installed golang with apk in the redis container :)
What's the easiest way to cache registries like docker, pypi, and npm these days?
There are still some we pull from Docker Hub, especially in the build process of our own images.
To work around that, on AWS, you can prefix the image with public.ecr.aws/docker/library/ for example public.ecr.aws/docker/library/python:3.12 and it will pull from AWS's mirror of Docker Hub.
Earlier quoted context omitted.
You pull the images you want to use, preferably with some automated process, then push them to your own repo. And anyways use your own repo when pulling for dev/production. It saves you from images disappearing as well.
What do you like using for your own repo? Artifactory? Something else?