This repository has been archived by the owner on Sep 12, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 880
/v1/users gives 404 if specifying DOCKER_REGISTRY_CONFIG #478
Comments
Appears this is a regression introduced in 0.7.2. The above command worked fine when run against 0.7.1. |
Same config running against 0.7.1 vs 0.7.2. The standalone mode stays the same in the headers, but still no users endpoint:
|
Please use 0.7.3 |
That's what I am using. I just was trying to help by figuring out where the bug was introduced. |
Can you copy your config_sample.yml ? Thanks. |
Put otherwise: are you sure you copied config_sample from 0.7.3 and not from master? Here, things work OK when using the config from 0.7.3 with registry 0.7.3 - and they don't when using config from master with registry 0.7.3 (which is expected, given #444). Can you confirm? |
Yes that was the issue! Thanks. Did seem a bit too strange to be real. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I take the standard container and run it via:
docker run -i -t -p 5000:5000 registry:0.7.3
I am succesfully able to curl /v1/users/ endpoint. If I specify a config override using an exact copy of config-sample.yml, I get 404:
docker run -i -t -p 5000:5000 -v
pwd:/etc/docker-config -e DOCKER_REGISTRY_CONFIG="/etc/docker-config/config-sample.yml" registry:0.7.3
I know this sounds weird, but it is 100% reproducible. It's the same config file so it should have the same standalone=true.
The text was updated successfully, but these errors were encountered: