From 82366daf7cf72537f7e53225a68ca18c82538fe2 Mon Sep 17 00:00:00 2001 From: Laura Brehm Date: Fri, 30 Aug 2024 12:24:06 +0100 Subject: [PATCH] release notes: add known issue for CLI login address normalization Signed-off-by: Laura Brehm --- content/desktop/release-notes.md | 6 ++++++ content/engine/release-notes/27.md | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/content/desktop/release-notes.md b/content/desktop/release-notes.md index efca1135fd..3be1619a01 100644 --- a/content/desktop/release-notes.md +++ b/content/desktop/release-notes.md @@ -71,6 +71,12 @@ Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/pro - Fixed a bug that caused WSL distro to terminate abruptly. Fixes [for-win/14230](https://github.com/docker/for-win/issues/14230). - Fixed an issue that caused WSL to update in each startup. Fixes [for-win/13868](https://github.com/docker/for-win/issues/13868), [for-win/13806](https://github.com/docker/for-win/issues/13806). +### Known Issues + +- There is a known issue when authenticating against a registry in the Docker CLI (`docker login [registry address]`) where, if the provided registry address includes a repository/image name (such as `docker login index.docker.io/docker/welcome-to-docker`), the repository part (`docker/welcome-to-docker`) is not normalized and results in credentials being stored incorrectly, which causes subsequent pulls from the registry (`docker pull index.docker.io/docker/welcome-to-docker`) to not be authenticated. To prevent this, don't include any extraneous suffix in the registry address when running `docker login`. + > [!NOTE] + > Using `docker login` with an address that includes URL path segments is not a documented use case and is considered unsupported. The recommended usage is to specify only a registry hostname, and optionally a port, as the address for `docker login`. + ## 4.33.1 {{< release-date date="2024-07-31" >}} diff --git a/content/engine/release-notes/27.md b/content/engine/release-notes/27.md index 36ab3d5242..179327248b 100644 --- a/content/engine/release-notes/27.md +++ b/content/engine/release-notes/27.md @@ -93,6 +93,12 @@ if an image is a multi-platform image. - Update Compose to [v2.29.2](https://github.com/docker/compose/releases/tag/v2.29.2). [docker/docker-ce-packaging#1050](https://github.com/docker/docker-ce-packaging/pull/1050) - Update containerd to [v1.7.21](https://github.com/containerd/containerd/releases/tag/v1.7.21). [moby/moby#48383](https://github.com/moby/moby/pull/48383), [docker/containerd-packaging#389](https://github.com/docker/containerd-packaging/pull/389) +### Known Issues + +- There is a known issue when authenticating against a registry in the Docker CLI (`docker login [registry address]`) where, if the provided registry address includes a repository/image name (such as `docker login index.docker.io/docker/welcome-to-docker`), the repository part (`docker/welcome-to-docker`) is not normalized and results in credentials being stored incorrectly, which causes subsequent pulls from the registry (`docker pull index.docker.io/docker/welcome-to-docker`) to not be authenticated. To prevent this, don't include any extraneous suffix in the registry address when running `docker login`. + > [!NOTE] + > Using `docker login` with an address that includes URL path segments is not a documented use case and is considered unsupported. The recommended usage is to specify only a registry hostname, and optionally a port, as the address for `docker login`. + ## 27.1 Release notes for Docker Engine version 27.1 releases.