-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
registry: don't call "/info" API endpoint to get default registry #2819
registry: don't call "/info" API endpoint to get default registry #2819
Conversation
@tiborvass @tonistiigi PTAL WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 😻
There's one thing I need to check; I'm looking at changing the default in docker/engine from the old |
66b90b5
to
8eeba85
Compare
8eeba85
to
1481863
Compare
Codecov Report
@@ Coverage Diff @@
## master #2819 +/- ##
==========================================
- Coverage 59.05% 59.01% -0.04%
==========================================
Files 284 284
Lines 23852 23833 -19
==========================================
- Hits 14086 14066 -20
- Misses 8907 8908 +1
Partials 859 859 |
1481863
to
29cbb94
Compare
The CLI currenly calls the `/info` endpoint to get the address of the default registry to use. This functionality was added as part of the initial Windows implementation of the engine. For legal reasons, Microsoft Windows (and thus Docker images based on Windows) were not allowed to be distributed through non-Microsoft infrastructure. As a temporary solution, a dedicated "registry-win-tp3.docker.io" registry was created to serve Windows images. As a result, the default registry was no longer "fixed", so a helper function (`ElectAuthServer`) was added to allow the CLI to get the correct registry address from the daemon. (docker/docker PR's/issues 18019, 19891, 19973) Using separate registries was not an ideal solution, and a more permanent solution was created by introducing "foreign image layers" in the distribution spec, after which the "registry-win-tp3.docker.io" ceased to exist, and removed from the engine through docker/docker PR 21100. However, the `ElectAuthServer` was left in place, quoting from that PR; > make the client check which default registry the daemon uses is still > more correct than leaving it up to the client, even if it won't technically > matter after this PR. There may be some backward compatibility scenarios > where `ElectAuthServer` [sic] is still helpful. That comment was 5 years ago, and given that the engine and cli are released in tandem, and the default registry is not configurable, we can save the extra roundtrip to the daemon by using a fixed value. This patch deprecates the `ElectAuthServer` function, and makes it return the default registry without calling (potentially expensie) `/info` API endpoint. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
29cbb94
to
b4ca1c7
Compare
Thx! Okay let's get this one in 👍 |
The CLI currenly calls the
/info
endpoint to get the address of the default registry to use.This functionality was added as part of the initial Windows implementation of the engine. For legal reasons, Microsoft Windows (and thus Docker images based on Windows) were not allowed to be distributed through non-Microsoft infrastructure. As a temporary solution, a dedicated "registry-win-tp3.docker.io" registry was created to serve Windows images.
As a result, the default registry was no longer "fixed", so a helper function (
ElectAuthServer
) was added to allow the CLI to get the correct registry address from the daemon. (docker/docker PR's/issues 18019, 19891, 19973)Using separate registries was not an ideal solution, and a more permanent solution was created by introducing "foreign image layers" in the distribution spec, after which the "registry-win-tp3.docker.io" ceased to exist, and removed from the engine through moby/moby#21100.
However, the
ElectAuthServer
was left in place, quoting from that PR;That comment was 5 years ago, and given that the engine and cli are released in tandem, and the default registry is not configurable, we can save the extra roundtrip to the daemon by using a fixed value.
This patch deprecates the
ElectAuthServer
function, and makes it return the default registry without calling (potentially expensive)/info
API endpoint.- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)