publish updates from main (#22155)

Automated pull request for publishing docs updates.

---------

Signed-off-by: Craig <[email protected]>
Signed-off-by: Lorena Rangel <[email protected]>
Co-authored-by: sheltongraves <[email protected]>
Co-authored-by: Craig Osterhout <[email protected]>
Co-authored-by: Allie Sadler <[email protected]>
Co-authored-by: Lorena Rangel <[email protected]>

Author: 4 people

content/manuals/_index.md

@@ -59,6 +59,10 @@ params:
     description: Run integration tests, with real dependencies, in the cloud.
     icon: package_2
     link: https://testcontainers.com/cloud/docs/
+  - title: Docker Projects
+    description: Use a unified, project-based workflow to run your containerized projects. 
+    icon: folder
+    link: /projects/
   platform:
   - title: Administration
     description: Centralized observability for companies and organizations.

content/manuals/desktop/features/desktop-cli.md

@@ -13,7 +13,7 @@ params:
 
 {{< summary-bar feature_name="Docker Desktop CLI" >}}
 
-The Docker Desktop CLI lets you perform key operations such as starting, stopping, restarting, and checking the status of Docker Desktop directly from the command line.
+The Docker Desktop CLI lets you perform key operations such as starting, stopping, restarting, and updating Docker Desktop directly from the command line.
 
 The Docker Desktop CLI provides:
 
@@ -36,7 +36,8 @@ docker desktop COMMAND [OPTIONS]
 | `status`             | Displays whether Docker Desktop is running or stopped.       |
 | `engine ls`          | Lists available engines (Windows only)   |
 | `engine use`         | Switch between Linux and Windows containers (Windows only) |
-| `update`             | Manage Docker Desktop updates. Available for Mac only and with Docker Desktop version 4.38 and later. |
+| `update`             | Manage Docker Desktop updates. Available for Mac only with Docker Desktop version 4.38, or all OSs with Docker Desktop version 4.39 and later. |
+| `logs`               | Print log entries                        |
 
 
 For more details on each command, see the [Docker Desktop CLI reference](/reference/cli/docker/desktop/_index.md).

content/manuals/desktop/release-notes.md

@@ -29,6 +29,56 @@ For more frequently asked questions, see the [FAQs](/manuals/desktop/troubleshoo
 >
 > If you're experiencing malware detection issues on Mac, follow the steps documented in [docker/for-mac#7527](https://github.com/docker/for-mac/issues/7527).
 
+## 4.39.0
+
+{{< release-date date="2025-03-05" >}}
+
+{{< desktop-install-v2 all=true beta_win_arm=true version="4.39.0" build_path="/184744/" >}}
+
+### New
+
+- The [Docker Desktop CLI](/manuals/desktop/features/desktop-cli.md) is now generally available. You can now also print logs with the new `docker desktop logs` command.
+- Docker Desktop now supports the `--platform` flag on [`docker load`](/reference/cli/docker/image/load.md) and [`docker save`](/reference/cli/docker/image/save.md). This helps you import and export a subset of multi-platform images.
+
+### Upgrades
+
+- [Docker Compose v2.33.1](https://github.com/docker/compose/releases/tag/v2.33.1)
+- [Docker Buildx v0.21.1](https://github.com/docker/buildx/releases/tag/v0.21.1)
+- [Kubernetes v1.32.2](https://github.com/kubernetes/kubernetes/releases/tag/v1.32.2)
+- [Docker Engine v28.0.1](https://docs.docker.com/engine/release-notes/28/#2801)
+- [Docker Scout CLI v1.16.3](https://github.com/docker/scout-cli/releases/tag/v1.16.3)
+
+### Bug fixes and enhancements
+
+#### For all platforms
+
+- Ask Gordon now offers deeper context on Docker images, containers, and volumes, delivers faster support, and enables more user actions via Docker Desktop and the Docker CLI.
+- Support multi-platform images via enabling users to pick a specific platform in `docker history`
+- Fixed an issue that caused clients other than the CLI and Docker Desktop to see a delay of 3 seconds whenever a container with port-mappings exists. See [docker/for-mac#7575](https://github.com/docker/for-mac/issues/7575)
+- Fixed a bug in the ECI Docker socket permissions which caused it to sometimes block Docker socket mounts on containers with allowed images, or images derived from allowed images.
+- Fixed a bug that prevented Docker Desktop from entering Resource Saver mode again immediately after an engine restart.
+
+#### For Mac
+
+- Downgraded Linux kernel to `v6.10.14` to fix a bug in OpenJDK that causes Java containers to terminate due to cgroups controller misidentification. See [docker/for-mac#7573](https://github.com/docker/for-mac/issues/7573).
+- Added `/usr/share/misc/usb.ids` in the root mount namespace to fix `usbip`.
+- Fixed an issue where the display of the CPU limit was capped at 8 when using Docker VMM.
+- Fixed an issue where startup would hang and the `com.docker.backend` process consumed 100% of the CPU. See [docker/for-mac#6951](https://github.com/docker/for-mac/issues/6951).
+- Fixed a bug that caused all Java programs running on M4 Macbook Pro to emit a SIGILL error. See [docker/for-mac#7583](https://github.com/docker/for-mac/issues/7583).
+- Blocked startup on macOS 15.4 beta 1 since starting VMs will cause the host to crash, see https://developer.apple.com/documentation/macos-release-notes/macos-15_4-release-notes#Virtual-Machines.
+- Fixed an issue where the myIPAddress PAC file function retrieved the host IP from the wrong interface, causing incorrect proxy selection.
+
+#### For Windows
+
+- Fixed a bug that prevented `docker compose log` to stream when running apps in WSL.
+- Fixed a bug where Paketo buildpacks failed with Enhanced Container Isolation when Docker Desktop uses WSL.
+- Fixed a bug where the WSL 2 integration would fail if WSL Version 1 distributions are installed.
+- Fixed a bug that caused some CLI plugins update to fail if WSL distributions were enabled.
+
+#### For Linux
+
+- The **Software Updates** page in settings, now points to the latest available version available.
+
 ## 4.38.0
 
 {{< release-date date="2025-01-30" >}}
@@ -1425,7 +1475,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st
 
 #### For Mac
 
-- Fixed a kernel panic on Apple silicon Macs with macOS version below 12.5. Fixes [docker/for-mac#6975](https://github.com/docker/for-mac/issues/6975).
+- Fixed a kernel panic on Apple Silicon Macs with macOS version earlier than 12.5. Fixes [docker/for-mac#6975](https://github.com/docker/for-mac/issues/6975).
 - Fixed a bug where Docker Desktop failed to start if invalid directories were included in `filesharingDirectories`. Fixes [docker/for-mac#6980](https://github.com/docker/for-mac/issues/6980).
 - Fixed a bug where installer is creating root-owned directories. Fixes [docker/for-mac#6984](https://github.com/docker/for-mac/issues/6984).
 - Fixed a bug where installer is failing on setting up the docker socket when missing `/Library/LaunchDaemons`. Fixes [docker/for-mac#6967](https://github.com/docker/for-mac/issues/6967).

content/manuals/docker-hub/usage/pulls.md

@@ -65,9 +65,6 @@ Attribution is based on the following:
   organizations under the company, the pull is attributed to the user's personal
   namespace.
 
-When pulling Docker Verified Publisher images, attribution towards rate limiting
-is not applied. For more details, see [Docker Verified Publisher
-Program](/manuals/docker-hub/repos/manage/trusted-content/dvp-program.md).
 
 ### Authentication
 

content/manuals/projects/_index.md

@@ -0,0 +1,52 @@
+---
+title: Docker Projects
+params:
+  sidebar:
+    group: Products
+    badge:
+      color: blue
+      text: Beta
+weight: 50
+description: Learn how to use Docker Projects which provides a unified, project-based workflow to run your containerized projects. 
+keywords: Docker, projects, docker deskotp, containerization
+grid:
+- title: How Docker Projects works
+  description: Learn How Docker Projects works
+  icon: category
+  link: /projects/about/
+- title: Open a new project
+  description: Learn how to open a new local or remote projects.
+  icon: checklist
+  link: /projects/open/
+- title: Edit your project
+  description: Edit your project's run commands and setup. N
+  icon: design_services
+  link: /projects/edit/
+- title: Manage your projects
+  description: Run or remove your projects.
+  icon: tune
+  link: /projects/manage/
+- title: View your projects
+  description: View detailed information about your projects and services within your projects
+  icon: visibility
+  link: /projects/view/
+- title: FAQs
+  description: View common FAQs about Docker Projects
+  icon: help
+  link: /projects/faq/
+---
+
+{{< summary-bar feature_name="Docker Projects" >}}
+
+Docker Projects provides a simplified, project-based workflow for running and managing containerized applications. It organizes your code, configurations, and logs across local and cloud environments into a single view, making it easy to collaborate and share across teams.
+
+A project organizes your code and Docker artifacts into a single object. These artifacts include logs as well as customizable run commands. These artifacts can persist remotely in the cloud, which lets you access your projects from any device that has Docker Desktop.
+
+### Key features and benefits
+
+ - One-click project setup: Open a local folder or clone a Git repository and run your project instantly.
+ - Minimal Docker expertise required: Ideal for both beginners and experienced developers.
+ - Custom `run` commands for your projects: Define and store pre-configured `run` commands that are equivalent to running `docker compose up`.
+ - Local and remote projects: Work on projects locally or sync artifacts to the cloud for cross-device access and easy collaboration.
+
+{{< grid >}}

content/manuals/projects/about.md

@@ -0,0 +1,45 @@
+---
+title: How it works
+description: Understand how Docker Projects works 
+keywords: docker projects
+weight: 10
+---
+
+Docker Projects requires a Compose file (`compose.yml`) to define your application's services, networks, and configurations. When you open a project, Docker Projects automatically detects the Compose file, allowing you to configure and run services with pre-set commands. 
+
+By integrating with Docker Compose, Docker Projects ensures a consistent, easy-to-manage workflow for both individual developers and teams. Whether you're starting a new project, configuring it, or collaborating with a team, Docker Projects keeps the process simple.
+
+Docker Projects works as follows:
+
+1. Create or open a project. You can:
+
+   - Open a local project: Select a folder on your machine that contains your project code.
+   - Clone a Git repository: Provide a repository URL and clone the project into a local directory.
+
+   Once a project is opened, Docker Desktop detects the Compose file and prepares the project for execution.
+
+2. Configure and run your project with pre-configured commands. These commands:
+
+   - Work like `docker compose up`, launching services based on the Compose file.
+   - Can be customized with additional flags, multiple Compose files, and environment variables.
+   - Enable pre-run tasks, such as executing scripts before starting the services.
+
+   All of which means you can fine-tune your configurations without manually running complex CLI commands.
+
+3. Collaborate and share with teams. For projects linked to a Git repository, Docker Projects stores artifacts in the cloud, enabling easy collaboration:
+
+   - Work across devices: Open a project from any machine and instantly access stored configurations.
+   - Share configurations: Team members can access pre-defined run commands, reducing setup time.
+
+   Collaboration is easy — new developers can join a team, open a project, and start working without complex setup steps.
+
+4. Manage and iterate. Once a project is up and running, Docker Projects makes it easy to monitor, update, and troubleshoot:
+
+   - View logs to debug issues and track service activity.
+   - Edit configurations and run commands as requirements change.
+
+## What's next
+
+ - [Learn how to open a new project](/manuals/projects/open.md)
+ - [Explore common FAQs](/manuals/projects/faq.md)
+

content/manuals/projects/edit.md

@@ -0,0 +1,47 @@
+---
+title: Add or edit your run commands
+description: Learn how to add or edit your run commands in Docker Projects
+keywords: Docker, projects, docker deskotp, containerization, open, remote, local, run commands
+weight: 40
+---
+
+## Add a run command to a project
+
+1. Open an existing project and ensure that it is stopped.
+
+2. From the command drop-down menu, select **New run command**.
+
+3. Specify the following information for the run command:
+
+   > [!TIP]
+   >
+   > While configuring your run command, you can view the equivalent `docker compose up` command in the **Run command** section on the configuration page. You can also use this command to run your project from the command line. You can refer to the [`docker compose up` reference documentation](/reference/cli/docker/compose/up.md) to learn more about the options you configure.  
+
+   - **Name**: Specify a name to identify the run command.
+   - **Compose files**: Select one or more Compose files from your project. 
+   - **Flags**: Optionally, select one or more flags for your run command.
+
+   > [!TIP]
+   > 
+   > While the `--env-file` flag isn't currently supported, you can specify environment variables in your Compose file, or use the **Tasks** option to run a script that sets your environment variables. 
+
+   - **Services that will run**: After selecting one or more Compose files, the services defined in the files will appear here. If there is more than one service, you can optionally choose to not run a service by deselecting the checkbox.
+   - **Tasks (Advanced options)**: Optionally specify a command to run before running the project. For example, if you want to run a bash script from the project directory named `set-vars.sh`, you can specify bash `set-vars.sh`. Or, on Windows, to run a script with `cmd.exe` named `set-vars.bat`, specify `set-vars.bat`. Note that a task can access environment variables from your terminal profile, but it can't access local shell functions nor aliases.
+
+4. Select **Save changes**. 
+
+You can now select the new run command from the drop-down menu after opening the project.
+
+## Edit a run command
+
+1. Open an existing project and ensure that it is stopped.
+
+2. Select the run command you want to change from the command drop-down menu.
+
+3. Select the **Edit** icon next to the **Run** button.
+
+4. Specify your changes and then select **Save changes**.
+
+## What's next?
+
+ - [Manage your projects](/manuals/projects/manage.md)

content/manuals/projects/faq.md

@@ -0,0 +1,22 @@
+---
+title: Docker Projects FAQs
+linkTitle: FAQs
+description: Find common FAQs for Docker Projects
+keywords: faqs, docker projects, local, remote
+weight: 70
+---
+
+## Why is a Compose file required?
+
+A Compose file (`compose.yml`) defines how your application's containers should run together, including:
+
+ - Services (e.g., web, database, API)
+ - Networks for inter-container communication
+ - Volumes for persistent data storage
+ - Environment variables and configurations
+
+Without a Compose file, Docker Projects doesn't have a way to understand how your application should be structured or executed.
+
+## What if my project doesn’t have a Compose file?
+
+If your project doesn't include a `compose.yml` file, you need to create one before opening it in Docker Projects. 

content/manuals/projects/manage.md

@@ -0,0 +1,37 @@
+---
+title: Manage your projects
+description: Learn how to delete or completely remove a project.
+keywords: Docker, projects, docker deskotp, containerization, open, remote, local
+weight: 50
+---
+
+## Run a project or service
+
+1. Open a new or existing project.
+
+2. Select a run command from the drop-down menu.
+
+3. Select the **Run** button for the project or the **Play** button next to the service you'd like to run.
+
+## Stop or restart a project or service
+
+1. Open an existing project that is running.
+
+2. Select the **Stop** or **Restart** button for the project or the appropriate button next to the service.
+
+## Remove a project from Docker Desktop
+
+If a project is associated with a Git repository, you can remove it from Docker Desktop. When a project is deleted, you can no longer run the project from the **Projects** view, but its run configuration still exists remotely in the cloud. 
+
+This means that you can later [open the project](/manuals/projects/open.md#open-an-existing-remote-project) and associate it with the remote run configuration without having to specify the run command again.
+None of your local code is deleted when removing a project from Docker Desktop.
+
+To remove a project from Docker Desktop:
+
+1. Sign in to Docker Desktop, and go to **Projects**.
+
+2. Select the **More actions** menu next to the project, and then select **Remove from Docker Desktop**.
+
+## Delete a project
+
+Deleting a project removes it from Docker Desktop and deletes all configuration locally and remotely from the cloud. When a project is deleted, you can no longer run the project from the **Projects** view. None of your local code is deleted when you delete a project from Docker Desktop.