more freshness

Author: aevesdocker

content/manuals/desktop/features/containerd.md

@@ -1,44 +1,38 @@
 ---
 title: containerd image store
-weight: 60
+weight: 80
 description: How to activate the containerd integration feature in Docker Desktop
 keywords: Docker, containerd, engine, image store, lazy-pull
 toc_max: 3
 aliases:
 - /desktop/containerd/
 ---
 
-This page provides information about the ongoing integration of `containerd` for
-image and file system management in the Docker Engine.
+Docker Desktop is transitioning to use containerd for image and filesystem management. This page outlines the benefits, setup process, and new capabilities enabled by the containerd image store.
 
 > [!NOTE]
 > 
-> Images and containers are not shared between the classic image store and the
-> new containerd image store. When you switch image stores, containers and
-> images from the inactive store remain but are hidden until you switch back.
+> Docker Desktop maintains separate image stores for the classic and containerd image stores.
+> When switching between them, images and containers from the inactive store remain on disk but are hidden until you switch back.
 
-## What is containerd?
+## What is `containerd`?
 
-`containerd` is an abstraction of the low-level kernel features
-used to run and manage containers on a system.
-It's a platform used in container software like Docker and Kubernetes.
+`containerd` is a container runtime that provides a lightweight, consistent interface for container lifecycle management. It is already used under the hood by Docker Engine for creating, starting, and stopping containers.
 
-Docker Engine already uses `containerd` for container lifecycle management,
-which includes creating, starting, and stopping containers.
-This page describes the next step of the containerd integration for Docker:
-the containerd image store.
+Docker Desktop’s ongoing integration of containerd now extends to the image store, offering more flexibility and modern image support.
 
-## Image store
+## What is the `containerd` image store?
 
 The image store is the component responsible for pushing, pulling,
 and storing images on the filesystem.
+
 The classic Docker image store is limited in the types of images that it supports.
 For example, it doesn't support image indices, containing manifest lists.
 When you create multi-platform images, for example,
 the image index resolves all the platform-specific variants of the image.
 An image index is also required when building images with attestations.
 
-The containerd image store extends range of image types
+The containerd image store extends the range of image types
 that the Docker Engine can natively interact with.
 While this is a low-level architectural change,
 it's a prerequisite for unlocking a range of new use cases, including:
@@ -88,8 +82,4 @@ and load them to your local image store:
 
 <script async id="asciicast-ZSUI4Mi2foChLjbevl2dxt5GD" src="https://asciinema.org/a/ZSUI4Mi2foChLjbevl2dxt5GD.js"></script>
 
-## Feedback
 
-Thanks for trying the new features available with `containerd`. Give feedback or
-report any bugs you may find through the issues tracker on the
-[feedback form](https://dockr.ly/3PODIhD).

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

@@ -1,7 +1,7 @@
 ---
 title: Use the Docker Desktop CLI
 linkTitle: Docker Desktop CLI
-weight: 90
+weight: 100
 description: How to use the Docker Desktop CLI
 keywords: cli, docker desktop, macos, windows, linux
 ---

content/manuals/desktop/features/dev-environments/_index.md

@@ -3,7 +3,7 @@ description: Dev Environments
 keywords: Dev Environments, share, local, Compose
 title: Overview of Dev Environments
 linkTitle: Dev Environments 
-weight: 120
+weight: 130
 aliases:
 - /desktop/dev-environments/
 params:

content/manuals/desktop/features/gordon/_index.md

@@ -17,23 +17,22 @@ of the Docker ecosystem.
 
 ## What is Ask Gordon?
 
-Ask Gordon is a suite of AI-powered capabilities integrated into Docker's tools.
-These features, currently in Beta, are not enabled by default, and are not
-production-ready. You may also encounter the term "Docker AI" as a broader
-reference to this technology.
+Ask Gordon provides AI-powered assistance in Docker tools. It offers contextual help for tasks like:
+
+- Improving Dockerfiles
+- Running and troubleshooting containers
+- Interacting with your images and code
+- Finding vulnerabilities or configuration issues
 
-The goal of Ask Gordon is to make Docker's tools for managing images and
-containers more intuitive and accessible. It provides contextual assistance
-tailored to your local environment, including Dockerfiles, containers, and
-applications.
+It understands your local environment, including source code, Dockerfiles, and images, to provide personalized and actionable guidance.
 
-Ask Gordon integrates directly with Docker's tools to help you perform specific
-tasks. It understands your local setup, such as your local source code and
-images. For example, you can ask Gordon to help you identify vulnerabilities in
-your project or how to optimize a Dockerfile in your local repository. This
-tight integration ensures responses are practical and actionable.
+These features are not enabled by default, and are not
+production-ready. You may also encounter the term "Docker AI" as a broader
+reference to this technology.
 
-> [!NOTE] Ask Gordon is powered by Large Language Models (LLMs). Like all
+> [!NOTE] 
+>
+> Ask Gordon is powered by Large Language Models (LLMs). Like all
 > LLM-based tools, its responses may sometimes be inaccurate. Always verify the
 > information provided.
 
@@ -81,55 +80,32 @@ making it more effective for all users.
 If you have concerns about data collection or usage, you can
 [disable](#disable-ask-gordon) the feature at any time.
 
-## Setup
-
-To use this feature, you must have:
-
-- Docker Desktop version 4.38 or later.
-
-Ask Gordon is not enabled by default. To enable the feature:
-
-1. [Sign in](#sign-in) to your Docker account.
-2. [Enable the feature](#enable-the-feature) in the Docker Desktop settings.
+## Enable Ask Gordon
 
-### Sign in
-
-1. Open Docker Desktop.
-2. Select the **Sign in** button.
-3. Complete the sign-in process in your web browser.
-
-### Enable the feature
-
-After signing in to your Docker Account, enable the Docker AI feature:
-
-1. Navigate to the **Features in development** tab in settings.
-2. Under the **Experimental features** tab, select **Access experimental features**.
-3. Select **Apply and restart**. 
-4. Quit and reopen Docker Desktop to ensure the changes take effect. 
-5. Open the **Settings** view in Docker Desktop.
-6. Navigate to **Features in development**.
-7. From the **Beta** tab, check the **Enable Docker AI** checkbox.
+1. Sign in to your Docker account.
+2. Navigate to the **Features in development** tab in settings.
+3. Under the **Experimental features** tab, select **Access experimental features**.
+4. Select **Apply and restart**. 
+5. Quit and reopen Docker Desktop to ensure the changes take effect. 
+6. Open the **Settings** view in Docker Desktop.
+7. Navigate to **Features in development**.
+8. From the **Beta** tab, check the **Enable Docker AI** checkbox.
 
    The Docker AI terms of service agreement is displayed. You must agree to the
    terms before you can enable the feature. Review the terms and select **Accept
    and enable** to continue.
 
-8. Select **Apply & restart**.
+9. Select **Apply & restart**.
 
 ## Using Ask Gordon
 
 The primary interfaces to Docker's AI capabilities are through the **Ask
 Gordon** view in Docker Desktop, or if you prefer to use the CLI: the `docker
 ai` CLI command.
 
-If you've used an AI chatbot before, these interfaces will be pretty familiar to
-you. You can chat with the Docker AI to get help with your Docker tasks.
-
-### Contextual help
-
 Once you've enabled the Docker AI features, you'll also find references to **Ask
 Gordon** in various other places throughout the Docker Desktop user interface.
-Whenever you encounter a button with the "sparkles" (✨) icon in the user
+Whenever you encounter a button with the **Sparkles** (✨) icon in the user
 interface, you can use the button to get contextual support from Ask Gordon.
 
 ## Example workflows
@@ -179,7 +155,7 @@ able to help you get set up:
 2. Open the **Images** view in Docker Desktop and select the image.
 3. Select the **Run** button.
 
-In the _Run a new container_ dialog that opens, you should see a message about
+In the **Run a new containe** dialog, you should see a message about
 **Ask Gordon**.
 
 ![Ask Gordon hint in Docker Desktop](../../images/gordon-run-ctr.png)
@@ -218,13 +194,17 @@ across several dimensions:
 
 ## Disable Ask Gordon
 
+### For individual users
+
 If you've enabled Ask Gordon and you want to disable it again:
 
 1. Open the **Settings** view in Docker Desktop.
 2. Navigate to **Features in development**.
 3. Clear the **Enable Docker AI** checkbox.
 4. Select **Apply & restart**.
 
+### For organizations
+
 If you want to disable Ask Gordon for your entire Docker organization, using
 [Settings
 Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md),
@@ -271,4 +251,4 @@ here's how you can get in touch:
   the **Ask Gordon** view in Docker Desktop, or from the CLI by running the
   `docker ai feedback` command.
 
-Thank you for helping us improve Ask Gordon.
+

content/manuals/desktop/features/synchronized-file-sharing.md

@@ -1,6 +1,6 @@
 ---
 title: Synchronized file shares
-weight: 50
+weight: 70
 description: Get started with Synchronized file shares on Docker Desktop.
 keyword: mutagen, file sharing, docker desktop, bind mounts
 aliases:
@@ -40,7 +40,7 @@ After creating a file share instance, any container using a bind mount that poin
 To create a file share instance:
 1. Sign in to Docker Desktop.
 2. In **Settings**, navigate to the **File sharing** tab within the **Resources** section. 
-3. In the **Synchronized File Shares** section, select the **Create share** icon.
+3. In the **Synchronized file shares** section, select **Create share**.
 4. Select a host folder to share. The synchronized file share should initialize and be usable.
 
 File shares take a few seconds to initialize as files are copied into the Docker Desktop VM. During this time, the status indicator displays **Preparing**. There is also a status icon in the footer of the Docker Desktop Dashboard that keeps you updated.
@@ -53,7 +53,7 @@ When the status indicator displays **Watching for filesystem changes**, your fil
 
 > [!TIP]
 >
-> Compose can now automatically create file shares for bind mounts. 
+> Docker Compose can automatically create file shares for bind mounts. 
 > Ensure you're signed in to Docker with a paid subscription and have enabled both **Access experimental features** and **Manage Synchronized file shares with Compose** in Docker Desktop's settings.
 
 ## Explore your file share instance
@@ -93,11 +93,3 @@ In general, use your `.syncignore` file to exclude items that aren't critical to
 - POSIX-style Windows paths are not supported. Avoid setting the [`COMPOSE_CONVERT_WINDOWS_PATHS`](/manuals/compose/how-tos/environment-variables/envvars.md#compose_convert_windows_paths) environment variable in Docker Compose.
 
 - If you don't have the correct permissions to create symbolic links and your container attempts to create symbolic links in your file share instance, an **unable to create symbolic link** error message displays. For Windows users, see Microsoft's [Create symbolic links documentation](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/create-symbolic-links) for best practices and location of the **Create symbolic links** security policy setting. For Mac and Linux users, check that you have write permissions on the folder.
-
-## Feedback and support
-
-To give feedback or report bugs, visit:
-
-- [Docker Desktop for Mac issues on GitHub](https://github.com/docker/for-mac/issues)
-- [Docker Desktop for Windows issues on GitHub](https://github.com/docker/for-win/issues)
-- [Docker Desktop for Linux issues on GitHub](https://github.com/docker/desktop-linux/issues)

content/manuals/desktop/features/usbip.md

@@ -1,7 +1,7 @@
 ---
 title: Using USB/IP with Docker Desktop
 linkTitle: USB/IP support
-weight: 80
+weight: 50
 description: How to use USB/IP in Docker Desktop
 keywords: usb, usbip, docker desktop, macos, windows, linux
 toc_max: 3

content/manuals/desktop/features/vmm.md

@@ -3,7 +3,7 @@ title: Virtual Machine Manager for Docker Desktop on Mac
 linkTitle: Virtual Machine Manager 
 keywords: virtualization software, resource allocation, mac, docker desktop, vm monitoring, vm performance, apple silicon
 description: Discover Docker Desktop for Mac's Virtual Machine Manager (VMM) options, including the new Docker VMM for Apple Silicon, offering enhanced performance and efficiency
-weight: 100
+weight: 110
 aliases:
 - /desktop/vmm/
 ---

content/manuals/desktop/features/wasm.md

@@ -1,6 +1,6 @@
 ---
 title: Wasm workloads 
-weight: 20
+weight: 90
 description: How to run Wasm workloads with Docker Desktop
 keywords: Docker, WebAssembly, wasm, containerd, engine
 toc_max: 3
@@ -15,13 +15,16 @@ params:
 
 {{< summary-bar feature_name="Wasm workloads" >}}
 
-Wasm (short for WebAssembly) is a fast, light alternative to the Linux and
-Windows containers you’re using in Docker today (with
-[some tradeoffs](https://www.docker.com/blog/docker-wasm-technical-preview/)).
+WebAssembly (Wasm) is a fast, light alternative Linux and
+Windows containers.  With Docker Desktop, you can now run Wasm workloads side by side with traditional containers.
 
-This page provides information about the new ability to run Wasm applications
+This page provides information about the ability to run Wasm applications
 alongside your Linux containers in Docker.
 
+> [!TIP]
+>
+> Learn more about Wasm use cases and tradeoffs in the [Docker Wasm technical preview blog post](https://www.docker.com/blog/docker-wasm-technical-preview/).
+
 ## Turn on Wasm workloads
 
 Wasm workloads require the [containerd image store](containerd.md)
@@ -34,9 +37,7 @@ then pre-existing images and containers will be inaccessible.
 4. Select **Apply & restart** to save the settings.
 5. In the confirmation dialog, select **Install** to install the Wasm runtimes.
 
-Docker Desktop downloads and installs the following runtimes that you can use
-to run Wasm workloads:
-
+Docker Desktop downloads and installs the following runtimes: 
 - `io.containerd.slight.v1`
 - `io.containerd.spin.v2`
 - `io.containerd.wasmedge.v1`
@@ -211,16 +212,5 @@ Update your Docker Desktop to the latest version and try again.
 
 ## Known issues
 
-- Docker Compose may not exit cleanly when interrupted
-  - Workaround: Clean up `docker-compose` processes by sending them a SIGKILL
-    (`killall -9 docker-compose`).
-- Pushes to Hub might give an error stating
-  `server message: insufficient_scope: authorization failed`, even after logging
-  in using Docker Desktop
-  - Workaround: Run `docker login` in the CLI
-
-## Feedback
-
-Thanks for trying out Wasm workloads with Docker. Give feedback or report any
-bugs you may find through the issues tracker on the
-[public roadmap item](https://github.com/docker/roadmap/issues/426).
+- Docker Compose may not exit cleanly when interrupted. As a workaround, clean up `docker-compose` processes by sending them a SIGKILL (`killall -9 docker-compose`).
+- Pushes to Docker Hub might give an error stating `server message: insufficient_scope: authorization failed`, even after signing in through Docker Desktop. As a workaround, run `docker login` in the CLI

content/manuals/desktop/features/wsl/_index.md

@@ -5,7 +5,7 @@ keywords: wsl, wsl2, installing wsl2, wsl installation, docker wsl2, wsl docker,
   tech preview, wsl install docker, install docker wsl, how to install docker in wsl
 title: Docker Desktop WSL 2 backend on Windows
 linkTitle: WSL
-weight: 110
+weight: 120
 aliases:
 - /docker-for-windows/wsl/
 - /docker-for-windows/wsl-tech-preview/

data/summary.yaml

@@ -212,7 +212,6 @@ SSO:
   for: Administrators
 Synchronized file sharing:
   subscription: [Pro, Team, Business]
-  requires: Docker Desktop [4.27](/manuals/desktop/release-notes.md#4270) and later
 USB/IP support:
   requires: Docker Desktop [4.35.0](/manuals/desktop/release-notes.md#4350) and later
   for: Docker Desktop for Mac, Linux, and Windows with the Hyper-V backend