On November 20, 2020, Docker imposed rate limits on requests to its Docker Hub registry, affecting both anonymous and free users, which disrupted developer workflows worldwide. To circumvent the rate limits without incurring the cost of a service account, the author set up a pull-through cache, effectively acting as an intermediary to cache requests to Docker Hub and mitigate rate-limit failures. A pull-through cache allows users to fetch images from the upstream repository the first time and use the cached version for subsequent requests, which is particularly beneficial for images that do not change frequently. The article provides a detailed guide on configuring a pull-through cache using Docker's registry, addressing HTTPS issues with Let's Encrypt, and setting up authentication to secure private images. It also explores hosting the cache on a VPS, emphasizing cost-effectiveness and reliability, and suggests using tools like Earthly for further optimizing build performance.