dMp

you have to create the mentioned directory. And you have to do that on any host that wants to run docker accessing that registry, not on the registry host itself....

@mpas it does. You _might_ have to trust the cert at the OS level as well, though (since authentication here).

@Leon99 @mavogel the registry will always return 401 indiscriminately on both unauthorized access to existing images, and non-existent images, and there is no way to distinguish the two cases. This...

@mavogel unfortunately, I don't recall any clear documentation about that. I'm positive we did implement that on the Docker Hub (quite a few years ago) - maybe even in the...

Snippet for authenticated users: ```bash # 200 repo=library/nginx; user="XXX"; password="XXX"; curl "https://registry-1.docker.io/v2/$repo/manifests/latest" -v -o/dev/null -L -s -X GET -H "Authorization: Bearer $(curl "https://auth.docker.io/token?service=registry.docker.io&scope=repository%3A$repo%3Apull" -L -s -X GET -H "Authorization: Basic...

Ping @BrianBland do you want to help carry this through?

Hi @frol You should contact [email protected] for questions about the Hub.

Correct. @llamahunter > What's the progress on this issue? It seems strange that pull through proxy mirrors are supported for one registry (docker.io), but not any other registries. The reason...

@llamahunter yeah, I understand the need. Couple of thoughts: - images are fundamentally http cacheable objects, so, my expectation is that using a plain HTTP caching proxy (and configuring your...

@appleboy I'm confused about what the remaining issues are here (apart from the suckiness of compass itself). Is there a test-case I could use to reproduce the problem? Of master...