publish updates from main (#22871)

Automated pull request for publishing docs updates.

---------

Signed-off-by: Nicolas De Loof <[email protected]>
Signed-off-by: Guillaume Tardif <[email protected]>
Co-authored-by: Jack Green <[email protected]>
Co-authored-by: Jack Green <[email protected]>
Co-authored-by: Nicolas De loof <[email protected]>
Co-authored-by: Guillaume Tardif <[email protected]>
Co-authored-by: Craig Gumbley <[email protected]>
Co-authored-by: Allie Sadler <[email protected]>

Author: 5 people

_vendor/modules.txt

@@ -2,6 +2,6 @@
 # github.com/moby/buildkit v0.22.0
 # github.com/docker/buildx v0.24.0
 # github.com/docker/cli v28.2.2+incompatible
-# github.com/docker/compose/v2 v2.37.1
+# github.com/docker/compose/v2 v2.37.2
 # github.com/docker/model-cli v0.1.26-0.20250527144806-15d0078a3c01
 # github.com/docker/scout-cli v1.15.0

content/get-started/docker-concepts/the-basics/what-is-a-registry.md

@@ -19,7 +19,7 @@ Well, you can store your container images on your computer system, but what if y
 
 An image registry is a centralized location for storing and sharing your container images. It can be either public or private. [Docker Hub](https://hub.docker.com) is a public registry that anyone can use and is the default registry. 
 
-While Docker Hub is a popular option, there are many other available container registries available today, including [Amazon Elastic Container Registry(ECR)](https://aws.amazon.com/ecr/), [Azure Container Registry (ACR)](https://azure.microsoft.com/en-in/products/container-registry), and [Google Container Registry (GCR)](https://cloud.google.com/artifact-registry). You can even run your private registry on your local system or inside your organization. For example, Harbor, JFrog Artifactory, GitLab Container registry etc.
+While Docker Hub is a popular option, there are many other available container registries available today, including [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), [Azure Container Registry (ACR)](https://azure.microsoft.com/en-in/products/container-registry), and [Google Container Registry (GCR)](https://cloud.google.com/artifact-registry). You can even run your private registry on your local system or inside your organization. For example, Harbor, JFrog Artifactory, GitLab Container registry etc.
 
 ### Registry vs. repository
 

content/manuals/compose/releases/release-notes.md

@@ -15,6 +15,24 @@ For more detailed information, see the [release notes in the Compose repo](https
 
 ## 2.37.1
 
+{{< release-date date="2025-06-20" >}}
+
+### Bug fixes and enhancements
+
+- Introduce `use_api_socket`
+- Fixed `compose images` JSON output format
+- Fixed panic using `w` shortcut on project without watch support
+- Fixed a permission issue with bake metadata files on Windows
+- Fixed a panic error on provider service startup
+
+### Update
+
+- Dependencies upgrade: bump compose-go to v2.6.5
+- Dependencies upgrade: bump buildx to v0.25.0
+- Dependencies upgrade: bump buildkit to v0.23.0
+
+## 2.37.1
+
 {{< release-date date="2025-06-12" >}}
 
 ### Bug fixes and enhancements

content/manuals/desktop/setup/allow-list.md

@@ -24,6 +24,7 @@ This page contains the domain URLs that you need to add to a firewall allowlist
 | https://auth.docker.io                                                               | Authentication                               |
 | https://cdn.auth0.com                                                                | Authentication                               |
 | https://login.docker.com                                                             | Authentication                               |
+| https://auth.docker.com                                                              | Authentication                               |
 | https://desktop.docker.com                                                           | Update                                       |
 | https://hub.docker.com                                                               | Docker Hub                                   |
 | https://registry-1.docker.io                                                         | Docker Pull/Push                             |

content/manuals/desktop/setup/install/enterprise-deployment/msi-install-and-configure.md

@@ -34,7 +34,7 @@ The MSI package supports various MDM (Mobile Device Management) solutions, makin
 7. Follow the instructions on the installation wizard to authorize the installer and proceed with the install.
 8. When the installation is successful, select **Finish** to complete the installation process.
 
-If your administrator account is different from your user account, you must add the user to the **docker-users** group:
+If your administrator account is different from your user account, you must add the user to the **docker-users** group to access features that require higher privileges, such as creating and managing the Hyper-V VM, or using Windows containers:
 1. Run **Computer Management** as an **administrator**.
 2. Navigate to **Local Users and Groups** > **Groups** > **docker-users**.
 3. Right-click to add the user to the group.

content/manuals/desktop/setup/install/windows-install.md

@@ -180,7 +180,8 @@ again when you switch back.
 
 6. [Start Docker Desktop](#start-docker-desktop).
 
-If your administrator account is different to your user account, you must add the user to the **docker-users** group:
+If your administrator account is different to your user account, you must add the user to the **docker-users** group to access features that require higher privileges, such as creating and managing the Hyper-V VM, or using Windows containers:
+
 1. Run **Computer Management** as an **administrator**.
 2. Navigate to **Local Users and Groups** > **Groups** > **docker-users**. 
 3. Right-click to add the user to the group.
@@ -218,7 +219,7 @@ By default, Docker Desktop is installed at `C:\Program Files\Docker\Docker`.
 > Start-Process 'Docker Desktop Installer.exe' -Wait -ArgumentList 'install', '--accept-license'
 > ```
 
-If your admin account is different to your user account, you must add the user to the **docker-users** group:
+If your admin account is different to your user account, you must add the user to the **docker-users** group to access features that require higher privileges, such as creating and managing the Hyper-V VM, or using Windows containers.
 
 ```console
 $ net localgroup docker-users <user> /add

content/manuals/desktop/setup/install/windows-permission-requirements.md

@@ -18,12 +18,23 @@ Docker Desktop on Windows is designed with security in mind. Administrative righ
 
 ## Permission requirements
 
-While Docker Desktop on Windows can be run without having `Administrator` privileges, it does require them during installation. On installation you receive a UAC prompt which allows a privileged helper service to be installed. After that, Docker Desktop can be run without administrator privileges, provided you are members of the `docker-users` group. If you performed the installation, you are automatically added to this group, but other users must be added manually. This allows the administrator to control who has access to Docker Desktop.
+While Docker Desktop on Windows can be run without having `Administrator` privileges, it does require them during installation. On installation you receive a UAC prompt which allows a privileged helper service to be installed. After that, Docker Desktop can be run without administrator privileges. 
 
-The reason for this approach is that Docker Desktop needs to perform a limited set of privileged operations which are conducted by the privileged helper process `com.docker.service`. This approach allows, following the principle of least privilege, `Administrator` access to be used only for the operations for which it is absolutely necessary, while still being able to use Docker Desktop as an unprivileged user.
+Running Docker Desktop on Windows without the privileged helper does not require users to have `docker-users` group membership. However,
+some features that require privileged operations will have this requirement. 
+
+If you performed the installation, you are automatically added to this group, but other users must be added manually. This allows the administrator to control who has access to features that require higher privileges, such as creating and managing the Hyper-V VM, or using Windows containers.
+
+When Docker Desktop launches, all non-privileged named pipes are created so that only the following users can access them:
+- The user that launched Docker Desktop.
+- Members of the local `Administrators` group.
+- The `LOCALSYSTEM` account.
 
 ## Privileged helper
 
+Docker Desktop needs to perform a limited set of privileged operations which are conducted by the privileged helper process `com.docker.service`. This approach allows, following the principle of least privilege, `Administrator` access to be used only for the operations for which it is absolutely necessary, while still being able to use Docker Desktop as an unprivileged user.
+
+
 The privileged helper `com.docker.service` is a Windows service which runs in the background with `SYSTEM` privileges. It listens on the named pipe `//./pipe/dockerBackendV2`. The developer runs the Docker Desktop application, which connects to the named pipe and sends commands to the service. This named pipe is protected, and only users that are part of the `docker-users` group can have access to it.
 
 The service performs the following functionalities:

content/manuals/dhi/core-concepts/digests.md

@@ -122,5 +122,5 @@ Manifests:
 - Verification: You can pull and verify a specific image digest for your
   platform to ensure you're using the exact image version, not just the manifest
   list.
-- Poliqcy enforcement: When enforcing digest-based policies with Docker Scout,
+- Policy enforcement: When enforcing digest-based policies with Docker Scout,
   each platform variant is evaluated individually using its digest.

go.mod

@@ -5,7 +5,7 @@ go 1.24.0
 require (
 	github.com/docker/buildx v0.24.0 // indirect
 	github.com/docker/cli v28.2.2+incompatible // indirect
-	github.com/docker/compose/v2 v2.37.1 // indirect
+	github.com/docker/compose/v2 v2.37.2 // indirect
 	github.com/docker/model-cli v0.1.26-0.20250527144806-15d0078a3c01 // indirect
 	github.com/docker/scout-cli v1.15.0 // indirect
 	github.com/moby/buildkit v0.22.0 // indirect

hugo.yaml

@@ -140,7 +140,7 @@ params:
   # (Used to show e.g., "latest" and "latest"-1 in engine install examples
   docker_ce_version_prev: "28.1.0"
   # Latest Docker Compose version
-  compose_version: "v2.37.1"
+  compose_version: "v2.37.2"
   # Latest BuildKit version
   buildkit_version: "0.22.0"