4 ms·
Super easy to run a docker cache proxy: docker run -d -p 6000:5000 \ -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io \ --restart always \
by eblanshey 6y ago
Super easy to run a docker cache proxy:
docker run -d -p 6000:5000 \
-e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io \
--restart always \
--name registry registry:2
That's it. Now fetch docker images from the IP that command is running on. Taken from gitlab: https://docs.gitlab.com/runner/install/registry_and_cache_servers.html https://docs.gitlab.com/runner/install/registry_and_cache_se...
- kortex 6y agoI think this addition to docker/config.json should do the trick to make it hit the proxy? https://docs.docker.com/registry/recipes/mirror/#configure-the-docker-daemon https://docs.docker.com/registry/recipes/mirror/#configure-t...
- terom 6y agoIs that going to actually help with the manifest-based rate limits? It sounds like it only caches the layers, the manifest metadata for a tag is not cached. https://docs.docker.com/registry/recipes/mirror/#what-if-the-content-changes-on-the-hub https://docs.docker.com/registry/recipes/mirror/#what-if-the... > When a pull is attempted with a tag, the Registry checks the remote to ensure if it has the latest version of the requested content. Otherwise, it fetches and caches the latest content.
- eblanshey 6y agoHm you're right. I wonder if there's a way to cache a tag's metadata for a while...