From b7aaa755922e880b87a6281b7bf0e5372b415eef Mon Sep 17 00:00:00 2001 From: Lorena Rangel Date: Mon, 2 Sep 2024 12:11:05 +0200 Subject: [PATCH 1/3] add resource saver known issue Signed-off-by: Lorena Rangel --- content/desktop/release-notes.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/desktop/release-notes.md b/content/desktop/release-notes.md index 0bc097a6d929..3eb657544b84 100644 --- a/content/desktop/release-notes.md +++ b/content/desktop/release-notes.md @@ -74,11 +74,12 @@ Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/pro ### Known issues -- Compose Bridge does not work automatically when you enable it within the **Experimental** settings tab. It take a few minutes before you are notified that you must 'repair' Docker Desktop which then installs the `compose-bridge` binary. -- The **Convert and Deploy** button in the Compose file viewer might be disabled even when Kubernetes is running and Compose Bridge is enabled. The workaround for this is to disable Compose Bridge in the **Experimental** settings tab, apply the change with **Apply & restart**, then re-enable and select **Apply & restart** again. +- Compose Bridge does not work automatically when you enable it within the **Experimental** settings tab. It takes a few minutes before you are notified that you must 'repair' Docker Desktop which then installs the `compose-bridge` binary. +- The **Convert and Deploy** button in the Compose file viewer might be disabled even when Kubernetes is running and Compose Bridge is enabled. The workaround for this is to disable Compose Bridge in the **Experimental** settings tab, apply the change with **Apply & restart**, then re-enable and select **Apply & restart** again. - 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`. +- When running `docker compose up` and Resource Saver mode is enabled, the command is unresponsive. As a workaround you can manually exit the Resource Saving mode for docker compose to become responsive again. ## 4.33.1 From 6a8f6754d8d3565f0c257cd28b31d8264c64cebe Mon Sep 17 00:00:00 2001 From: Lorena Rangel Date: Mon, 2 Sep 2024 15:35:50 +0200 Subject: [PATCH 2/3] Update content/desktop/release-notes.md Co-authored-by: Mihaela Stoica --- content/desktop/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/desktop/release-notes.md b/content/desktop/release-notes.md index 3eb657544b84..9c913a5542ff 100644 --- a/content/desktop/release-notes.md +++ b/content/desktop/release-notes.md @@ -79,7 +79,7 @@ Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/pro - 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`. -- When running `docker compose up` and Resource Saver mode is enabled, the command is unresponsive. As a workaround you can manually exit the Resource Saving mode for docker compose to become responsive again. +- When running `docker compose up` and Docker Desktop is in the Resource Saver mode, the command is unresponsive. As a workaround you can manually exit the Resource Saving mode for docker compose to become responsive again. ## 4.33.1 From dbcc092334c99addb29efd497a355cfaa311e0a4 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Tue, 3 Sep 2024 07:58:38 +0100 Subject: [PATCH 3/3] Update content/desktop/release-notes.md --- content/desktop/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/desktop/release-notes.md b/content/desktop/release-notes.md index 9c913a5542ff..5d5b3e715829 100644 --- a/content/desktop/release-notes.md +++ b/content/desktop/release-notes.md @@ -79,7 +79,7 @@ Take a look at the [Docker Public Roadmap](https://github.com/docker/roadmap/pro - 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`. -- When running `docker compose up` and Docker Desktop is in the Resource Saver mode, the command is unresponsive. As a workaround you can manually exit the Resource Saving mode for docker compose to become responsive again. +- When running `docker compose up` and Docker Desktop is in the Resource Saver mode, the command is unresponsive. As a workaround, manually exit the Resource Saving mode and Docker Compose becomes responsive again. ## 4.33.1