I followed this guide to configure the Docker v2 registry, acting as the local proxy cache for Docker Hub images. My Docker daemon is configured with the --insecure-registry and --registry-mirror pointing to the same registry instance.
When pulling images, it works correctly, linking them to local storage.
The problem is that when I try to click an image on such a local private registry, I get a strange UNSUPPORTED error. The registry log states:
time="2015-11-09T13:20:22Z" level=error msg="response completed with error" err.code=UNSUPPORTED err.message="The operation is unsupported." go.version=go1.4.3 http.request.host="my.registry.io:5000" http.request.id=b1faccb3-f592-4790-bbba-00ebb3a3bfc1 http.request.method=POST http.request.remoteaddr="192.168.0.4:57608" http.request.uri="/v2/mygroup/myimage/blobs/uploads/" http.request.useragent="docker/1.9.0 go/go1.4.2 git-commit/76d6bc9 kernel/3.16.0-4-amd64 os/linux arch/amd64" http.response.contenttype="application/json; charset=utf-8" http.response.duration=2.035918ms http.response.status=405 http.response.written=78 instance.id=79970ec3-c38e-4ebf-9e83-c3890668b122 vars.name="mygroup/myimage" version=v2.2.0
If I turn off the proxy server settings in the registry, then clicking will work correctly. Am I missing something in the configuration, or is it just that the private registry cannot simultaneously act as a proxy cache?
docker docker-registry
Cristian greco
source share