ENGDOCS-2515c

Author: aevesdocker

content/manuals/desktop/features/containerd.md

@@ -1,6 +1,6 @@
 ---
 title: containerd image store
-weight: 10
+weight: 60
 description: How to activate the containerd integration feature in Docker Desktop
 keywords: Docker, containerd, engine, image store, lazy-pull
 toc_max: 3

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

@@ -1,14 +1,9 @@
 ---
-title: Using the Docker Desktop CLI
+title: Use the Docker Desktop CLI
 linkTitle: Docker Desktop CLI
-weight: 120
+weight: 90
 description: How to use the Docker Desktop CLI
 keywords: cli, docker desktop, macos, windows, linux
-params:
-  sidebar:
-    badge:
-      color: green
-      text: New
 ---
 
 {{< summary-bar feature_name="Docker Desktop CLI" >}}

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: 40
+weight: 120
 aliases:
 - /desktop/dev-environments/
 params:

content/manuals/desktop/features/gpu.md

@@ -1,7 +1,7 @@
 ---
-title: GPU support in Docker Desktop
+title: GPU support in Docker Desktop for Windows
 linkTitle: GPU support
-weight: 80
+weight: 40
 description: How to use GPU in Docker Desktop
 keywords: gpu, gpu support, nvidia, wsl2, docker desktop, windows
 toc_max: 3
@@ -13,22 +13,27 @@ aliases:
 >
 > Currently GPU support in Docker Desktop is only available on Windows with the WSL2 backend.
 
-## Using NVIDIA GPUs with WSL2
+Docker Desktop for Windows supports NVIDIA GPU Paravirtualization (GPU-PV) on NVIDIA GPUs, allowing containers to access GPU resources for compute-intensive workloads like AI, machine learning, or video processing.
 
-Docker Desktop for Windows supports WSL 2 GPU Paravirtualization (GPU-PV) on NVIDIA GPUs. To enable WSL 2 GPU Paravirtualization, you need:
+## Prerequisites
 
-- A machine with an NVIDIA GPU
+To enable WSL 2 GPU Paravirtualization, you need:
+
+- A Windows machine with an NVIDIA GPU
 - Up to date Windows 10 or Windows 11 installation
 - [Up to date drivers](https://developer.nvidia.com/cuda/wsl) from NVIDIA supporting WSL 2 GPU Paravirtualization
 - The latest version of the WSL 2 Linux kernel. Use `wsl --update` on the command line
 - To make sure the [WSL 2 backend is turned on](wsl/_index.md#turn-on-docker-desktop-wsl-2) in Docker Desktop
 
-To validate that everything works as expected, execute a `docker run` command with the `--gpus=all` flag. For example, the following will run a short benchmark on your GPU:
+## Validate GPU support
+
+To confirm GPU access is working inside Docker, run the following:
 
 ```console
 $ docker run --rm -it --gpus=all nvcr.io/nvidia/k8s/cuda-sample:nbody nbody -gpu -benchmark
 ```
-The output will be similar to:
+
+This runs an n-body simulation benchmark on the GPU. The output will be similar to:
 
 ```console
 Run "nbody -benchmark [-numbodies=<numBodies>]" to measure performance.
@@ -58,9 +63,16 @@ GPU Device 0: "GeForce RTX 2060 with Max-Q Design" with compute capability 7.5
 = 2724.379 single-precision GFLOP/s at 20 flops per interaction
 ```
 
-Or if you wanted to try something more useful you could use the official [Ollama image](https://hub.docker.com/r/ollama/ollama) to run the Llama2 large language model.
+## Run a real-world model: Llama2 with Ollama
+
+Use the [official Ollama image](https://hub.docker.com/r/ollama/ollama) to run the Llama2 LLM with GPU acceleration:
 
 ```console
 $ docker run --gpus=all -d -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama
+```
+
+Then start the model:
+
+```console
 $ docker exec -it ollama ollama run llama2
 ```

content/manuals/desktop/features/kubernetes.md

@@ -20,7 +20,7 @@ Kubernetes on Docker Desktop runs alongside other workloads, including Swarm ser
 
 ## What happens when I enable Kubernetes in Docker Desktop?
 
-When you enable Kubernetes in Docker Desktop, the following actions are triggered in the Docker Desktop backend and VM:
+The following actions are triggered in the Docker Desktop backend and VM:
 
 - Generation of certificates and cluster configuration
 - Download and installation of Kubernetes internal components

content/manuals/desktop/features/networking.md

@@ -2,6 +2,7 @@
 description: Understand how networking works on Docker Desktop and see the known limitations
 keywords: networking, docker desktop, proxy, vpn, Linux, Mac, Windows
 title: Explore networking features on Docker Desktop
+linkTitle: Networking
 aliases:
 - /desktop/linux/networking/
 - /docker-for-mac/networking/
@@ -11,11 +12,10 @@ aliases:
 - /docker-for-windows/networking/
 - /desktop/windows/networking/
 - /desktop/networking/
-weight: 50
+weight: 30
 ---
 
-Docker Desktop provides several networking features to make it easier to
-use.
+Docker Desktop includes built-in networking capabilities to help you connect containers with services on your host, across containers, or through proxies and VPNs.
 
 ## Networking features for all platforms
 
@@ -33,17 +33,21 @@ When you run a container with the `-p` argument, for example:
 $ docker run -p 80:80 -d nginx
 ```
 
-Docker Desktop makes whatever is running on port 80 in the container, in
-this case, `nginx`, available on port 80 of `localhost`. In this example, the
-host and container ports are the same. If, for example, you already have something running on port 80 of
-your host machine, you can connect the container to a different port:
+Docker Desktop makes whatever is running on port `80` in the container, in
+this case, `nginx`, available on port `80` of `localhost`. In this example, the
+host and container ports are the same. 
+
+To avoid conflicts with services already using port `80` on the host:
 
 ```console
 $ docker run -p 8000:80 -d nginx
 ```
 
-Now, connections to `localhost:8000` are sent to port 80 in the container. The
-syntax for `-p` is `HOST_PORT:CLIENT_PORT`.
+Now connections to `localhost:8000` are sent to port `80` in the container. 
+
+> [!TIP]
+>
+> The syntax for `-p` is `HOST_PORT:CLIENT_PORT`.
 
 ### HTTP/HTTPS Proxy support
 
@@ -53,10 +57,6 @@ See [Proxies](/manuals/desktop/settings-and-maintenance/settings.md#proxies)
 
 {{< summary-bar feature_name="SOCKS5 proxy support" >}}
 
-> [!NOTE]
->
-> Requires a Business subscription.
-
 SOCKS (Socket Secure) is a protocol that facilitates the routing of network packets between a client and a server through a proxy server. It provides a way to enhance privacy, security, and network performance for users and applications. 
 
 You can enable SOCKS proxy support to allow outgoing requests, such as pulling images, and access Linux container backend IPs from the host. 
@@ -72,7 +72,7 @@ To enable and set up SOCKS proxy support:
 
 ### SSH agent forwarding
 
-Docker Desktop on Mac and Linux allows you to use the host’s SSH agent inside a container. To do this:
+Docker Desktop for Mac and Linux lets you use the host’s SSH agent inside a container. To do this:
 
 1. Bind mount the SSH agent socket by adding the following parameter to your `docker run` command:
 
@@ -104,9 +104,9 @@ services:
 
 ### Changing internal IP addresses
 
-The internal IP addresses used by Docker can be changed from **Settings**. After changing IPs, it is necessary to reset the Kubernetes cluster and to leave any active Swarm.
+The internal IP addresses used by Docker can be changed from **Settings**. After changing IPs, you need to reset the Kubernetes cluster and to leave any active Swarm.
 
-### There is no docker0 bridge on the host
+### There is no `docker0` bridge on the host
 
 Because of the way networking is implemented in Docker Desktop, you cannot
 see a `docker0` interface on the host. This interface is actually within the
@@ -127,7 +127,7 @@ However if you are a Windows user, per-container IP addressing is possible with
 ### I want to connect from a container to a service on the host
 
 The host has a changing IP address, or none if you have no network access.
-We recommend that you connect to the special DNS name `host.docker.internal`,
+Docker recommends you connect to the special DNS name `host.docker.internal`,
 which resolves to the internal IP address used by the host.
 
 You can also reach the gateway using `gateway.docker.internal`.
@@ -154,7 +154,7 @@ If you have installed Python on your machine, use the following instructions as
 Port forwarding works for `localhost`. `--publish`, `-p`, or `-P` all work.
 Ports exposed from Linux are forwarded to the host.
 
-We recommend you publish a port, or to connect from another
+Docker recommends you publish a port, or to connect from another
 container. This is what you need to do even on Linux if the container is on an
 overlay network, not a bridge network, as these are not routed.
 

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

@@ -1,6 +1,6 @@
 ---
 title: Synchronized file shares
-weight: 30
+weight: 50
 description: Get started with Synchronized file shares on Docker Desktop.
 keyword: mutagen, file sharing, docker desktop, bind mounts
 aliases:

content/manuals/desktop/features/usbip.md

@@ -1,7 +1,7 @@
 ---
 title: Using USB/IP with Docker Desktop
 linkTitle: USB/IP support
-weight: 100
+weight: 80
 description: How to use USB/IP in Docker Desktop
 keywords: usb, usbip, docker desktop, macos, windows, linux
 toc_max: 3
@@ -11,15 +11,11 @@ aliases:
 
 {{< summary-bar feature_name="USB/IP support" >}}
 
-> [!NOTE]
->
-> Available on Docker Desktop for Mac, Linux, and Windows with the Hyper-V backend.
-
 USB/IP enables you to share USB devices over the network, which can then be accessed from within Docker containers. This page focuses on sharing USB devices connected to the machine you run Docker Desktop on. You can repeat the following process to attach and use additional USB devices as needed.
 
 > [!NOTE]
 >
-> The Docker Desktop VM kernel image comes pre-configured with drivers for many common USB devices, but Docker can't guarantee every possible USB device will work with this setup.
+> Docker Desktop includes built-in drivers for many common USB devices but Docker can't guarantee every possible USB device works with this setup.
 
 ## Setup and use
 
@@ -48,6 +44,8 @@ To attach the USB device, start a privileged Docker container with the PID names
 $ docker run --rm -it --privileged --pid=host alpine
 ```
 
+`--privileged` gives the container full access to the host, and `--pid=host` allows it to share the host’s process namespace.
+
 ### Step three: Enter the mount namespace of PID 1
 
 Inside the container, enter the mount namespace of the `init` process to gain access to the pre-installed USB/IP tools:
@@ -56,7 +54,7 @@ Inside the container, enter the mount namespace of the `init` process to gain ac
 $ nsenter -t 1 -m
 ```
 
-### Step four: Use USB/IP tools
+### Step four: Use the USB/IP tools
 
 Now you can use the USB/IP tools as you would on any other system:
 
@@ -102,7 +100,7 @@ Example output:
 event0  mice
 ```
 
-### Step five: Use the attached device in another container
+### Step five: Access the device from another container
 
 While the initial container remains running to keep the USB device operational, you can access the attached device from another container. For example:
 

content/manuals/desktop/features/vmm.md

@@ -3,23 +3,23 @@ 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: 110
+weight: 100
 aliases:
 - /desktop/vmm/
 ---
 
-{{< summary-bar feature_name="VMM" >}}
+Docker Desktop supports multiple Virtual Machine Managers (VMMs) to power the Linux VM that runs containers. You can choose the most suitable option based on your system architecture (Intel or Apple Silicon), performance needs, and feature requirements. This page provides an overview of the available options.
 
-The Virtual Machine Manager (VMM) in Docker Desktop for Mac is responsible for creating and managing the virtual machine used to run containers. Depending on your system architecture and performance needs, you can choose from multiple VMM options in Docker Desktop's [settings](/manuals/desktop/settings-and-maintenance/settings.md#general). This page provides an overview of the available options.
+To change the VMM, go to **Settings** > **General** > **Virtual Machine Manager**.
 
 ## Docker VMM
 
-Docker VMM is a new, container-optimized hypervisor introduced in Docker Desktop 4.35 and available on Apple Silicon Macs only. Its enhanced speed and resource efficiency makes it an ideal choice for optimizing your workflow.
+{{< summary-bar feature_name="VMM" >}}
 
-Docker VMM brings exciting advancements specifically tailored for Apple Silicon machines. By optimizing both the Linux kernel and hypervisor layers, Docker VMM delivers significant performance enhancements across common developer tasks.
+Docker VMM is a new, container-optimized hypervisor. By optimizing both the Linux kernel and hypervisor layers, Docker VMM delivers significant performance enhancements across common developer tasks.
 
 Some key performance enhancements provided by Docker VMM include:
- - Faster I/O operations: With a cold cache, iterating over a large shared filesystem with `find` is 2x faster than when the Apple Virtualization Framework is used.
+ - Faster I/O operations: With a cold cache, iterating over a large shared filesystem with `find` is 2x faster than when the Apple Virtualization framework is used.
  - Improved caching: With a warm cache, performance can improve by as much as 25x, even surpassing native Mac operations.
 
 These improvements directly impact developers who rely on frequent file access and overall system responsiveness during containerized development. Docker VMM marks a significant leap in speed, enabling smoother workflows and faster iteration cycles.
@@ -35,9 +35,9 @@ As Docker VMM is still in Beta, there are a few known limitations:
 - Docker VMM does not currently support Rosetta, so emulation of amd64 architectures is slow. Docker is exploring potential solutions.
 - Certain databases, like MongoDB and Cassandra, may fail when using virtiofs with Docker VMM. This issue is expected to be resolved in a future release.
 
-## Apple Virtualization Framework
+## Apple Virtualization framework
 
-The Apple Virtualization Framework is a stable and well-established option for managing virtual machines on Mac. It has been a reliable choice for many Mac users over the years. This framework is best suited for developers who prefer a proven solution with solid performance and broad compatibility.
+The Apple Virtualization framework is a stable and well-established option for managing virtual machines on Mac. It has been a reliable choice for many Mac users over the years. This framework is best suited for developers who prefer a proven solution with solid performance and broad compatibility.
 
 ## QEMU (Legacy) for Apple Silicon
 
@@ -47,7 +47,7 @@ The Apple Virtualization Framework is a stable and well-established option for m
 
 QEMU is a legacy virtualization option for Apple Silicon Macs, primarily supported for older use cases. 
 
-Docker recommends transitioning to newer alternatives, such as Docker VMM or the Apple Virtualization Framework, as they offer superior performance and ongoing support. Docker VMM, in particular, offers substantial speed improvements and a more efficient development environment, making it a compelling choice for developers working with Apple Silicon.
+Docker recommends transitioning to newer alternatives, such as Docker VMM or the Apple Virtualization framework, as they offer superior performance and ongoing support. Docker VMM, in particular, offers substantial speed improvements and a more efficient development environment, making it a compelling choice for developers working with Apple Silicon.
 
 Note that this is not related to using QEMU to emulate non-native architectures in [multi-platform builds](/manuals/build/building/multi-platform.md#qemu).
 

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: 90
+weight: 110
 aliases:
 - /docker-for-windows/wsl/
 - /docker-for-windows/wsl-tech-preview/