You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade from docker-ce 26.1.4 to docker-ce 27.0.1.
Run a build.
Expected Results
Successful build.
Actual Results
In console output received I received the following:
[Pipeline] withDockerRegistry
15:31:38 $ docker login -u dockerupload -p ******** https://myregistry.example.com:444/
15:31:38 WARNING! Using --password via the CLI is insecure. Use --password-stdin.
15:31:38 Error response from daemon: login attempt to https://myregistry.example.com/v2/ failed with status: 404 Not Found
[Pipeline] // withDockerRegistry
NOTE: The "docker login" line has the 444, the "Error" line does not.
I have verified that if I upgrade to docker v27, I my agent will only hit port 443, and if I downgrade to 26.1.4 it only hits 444.
I've verified that if I run, at the CLI on my agent machine: docker login https://myregistry.example.com:444/v2/ I get the 404 error (indicating it is going to the wrong port, also the "Error" line above):
Error response from daemon: login attempt to https://myregistry.example.com/v2/ failed with status: 404 Not Found
If I instead do: docker login myregistry.example.com:444 it reports:
Error response from daemon: login attempt to https://myregistry.example.com:444/v2/ failed with status: 401 Unauthorized
(I entered an invalid username/password for testing).
If I downgrade Docker to v26.1.4, both of the above commands produce the "401 Unauthorized" result.
I cannot change my "Declarative Pipeline (Docker)" settings to remove the https:// because Jenkins will error out with "Unknown protocol myregistry.example.com".
Anything else?
I'm opening a bug with Docker as well, as this seems to be a change that is not documented in their release notes.
Are you interested in contributing a fix?
I'm not able to contribute a fix.
The text was updated successfully, but these errors were encountered:
Docker has determined this is a regression, and has committed a PR to resolve this. Resolution for the moment is to revert to 26.1.4, until 27.0.2+ is available.
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Ubuntu 22.04
Reproduction steps
Expected Results
Successful build.
Actual Results
In console output received I received the following:
NOTE: The "docker login" line has the 444, the "Error" line does not.
I have verified that if I upgrade to docker v27, I my agent will only hit port 443, and if I downgrade to 26.1.4 it only hits 444.
I've verified that if I run, at the CLI on my agent machine:
docker login https://myregistry.example.com:444/v2/
I get the 404 error (indicating it is going to the wrong port, also the "Error" line above):If I instead do:
docker login myregistry.example.com:444
it reports:(I entered an invalid username/password for testing).
If I downgrade Docker to v26.1.4, both of the above commands produce the "401 Unauthorized" result.
I cannot change my "Declarative Pipeline (Docker)" settings to remove the https:// because Jenkins will error out with "Unknown protocol myregistry.example.com".
Anything else?
I'm opening a bug with Docker as well, as this seems to be a change that is not documented in their release notes.
Are you interested in contributing a fix?
I'm not able to contribute a fix.
The text was updated successfully, but these errors were encountered: