The Jenkins Docker plugin insists on prefixing the registry with "https://" (see above bug for details). After an upgrade to 27.0.1, this is now failing, reporting a 404 error reaching "https://myregistry.example.com/v2/" (note the missing :444).
At v26.1.4, both of these commands produce the same output:
docker login https://myregistry.example.com:444/
docker login myregistry.example.com:444
If I enter an invalid user/password, both of those report "401 Unauthorized".
Description
Also reported to Jenkins Docker Plugin here: https://github.com/jenkinsci/docker-plugin/issues/1082
The Jenkins Docker plugin insists on prefixing the registry with "https://" (see above bug for details). After an upgrade to 27.0.1, this is now failing, reporting a 404 error reaching "https://myregistry.example.com/v2/" (note the missing :444).
At v26.1.4, both of these commands produce the same output:
docker login https://myregistry.example.com:444/
docker login myregistry.example.com:444
If I enter an invalid user/password, both of those report "401 Unauthorized".
At 27.0.1, the second command produces the 401, but the first command reports a 404, with the URL "https://myregistry.example.com/v2/"
I have checked the 27.0.1 release notes and have seen nothing about a change related to the registry URL or docker login.
Reproduce
Detailed above.
Expected behavior
Detailed above.
docker version
docker info
Additional Info
No response