-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error pulling gcr.io/go-containerregistry/crane:debug #115
Comments
Hey @baby-gnu thanks for the report. I've still to find time to work on |
Just to toss in some 2c here. Having this same issue, but only when running in Github Actions, and with istio pilot:
Running on my local machine (M2 Macbook Pro), caching works as expected, but as of 11 September 2024 (when I first picked up on this) gcr.io is suddenly not working anymore. Edit: mkdir -p $(pwd)/docker/cache $(pwd)/docker/certs
echo "resolver 1.1.1.1 ipv6=off;" > $(pwd)/docker/resolvers.conf
docker run -d --name cache-docker \
-p 0.0.0.0:3128:3128 \
-e ENABLE_MANIFEST_CACHE=true \
-e REGISTRIES="quay.io ghcr.io registry.k8s.io gcr.io" \
--hostname cache-docker \
-v $(pwd)/docker/cache:/docker_mirror_cache \
-v $(pwd)/docker/certs:/ca \
-v $(pwd)/docker/resolvers.conf:/etc/nginx/resolvers.conf \
ghcr.io/rpardini/docker-registry-proxy:0.6.4-debug |
Hello.
I just setup the
docker-registry-proxy
which is working fine in most case but I have a strange issue aboutinvalid URL prefix
docker-registry-proxy logs for `docker pull gcr.io/go-containerregistry/crane:debug`
It's working fine with
gcr.io/kaniko-project/executor:debug
The text was updated successfully, but these errors were encountered: