docker · dvdksn · Jan 21, 2025 · Jan 17, 2025 · Jan 17, 2025 · Jan 17, 2025
diff --git a/Dockerfile b/Dockerfile
@@ -4,7 +4,7 @@
 ARG ALPINE_VERSION=3.21
 ARG GO_VERSION=1.23
 ARG HTMLTEST_VERSION=0.17.0
-ARG HUGO_VERSION=0.139.0
+ARG HUGO_VERSION=0.141.0
 ARG NODE_VERSION=22
 ARG PAGEFIND_VERSION=1.3.0
 

diff --git a/_vale/config/vocabularies/Docker/accept.txt b/_vale/config/vocabularies/Docker/accept.txt
@@ -154,6 +154,7 @@ Zsh
 [Vv]irtiofs
 [Vv]irtualize
 [Ww]alkthrough
+bootup
 cgroup
 config
 containerd

@@ -1,6 +1,6 @@
 # github.com/moby/moby v27.5.0+incompatible
-# github.com/moby/buildkit v0.18.1
-# github.com/docker/buildx v0.19.2
+# github.com/moby/buildkit v0.19.0
+# github.com/docker/buildx v0.20.0
 # github.com/docker/cli v27.5.0+incompatible
 # github.com/docker/compose/v2 v2.32.4
 # github.com/docker/scout-cli v1.15.0
diff --git a/content/get-started/docker-concepts/running-containers/sharing-local-files.md b/content/get-started/docker-concepts/running-containers/sharing-local-files.md
@@ -101,7 +101,7 @@ Using a bind mount, you can map the configuration file on your host computer to
     $ mkdir public_html
     ```
 
-3. Change the directory to `public_html` and create a file called `index.html` with the following content. This is a basic HTML document that creates a simple webpage that welcomes you with a friendly whale.
+3. Navigate into the newly created directory `public_html` and create a file called `index.html` with the following content. This is a basic HTML document that creates a simple webpage that welcomes you with a friendly whale.
 
     ```html
     <!DOCTYPE html>

diff --git a/content/get-started/workshop/06_bind_mounts.md b/content/get-started/workshop/06_bind_mounts.md
@@ -52,6 +52,9 @@ work.
 Docker Desktop's file sharing setting. This setting defines which parts of your
 filesystem you can share with containers. For details about accessing the setting, see [File sharing](/manuals/desktop/settings-and-maintenance/settings.md#file-sharing).
 
+    > [!NOTE]
+    > The **File sharing** tab is only available in Hyper-V mode, because the files are automatically shared in WSL 2 mode and Windows container mode.
+
 2. Open a terminal and change directory to the `getting-started-app`
    directory.
 

@@ -6,13 +6,6 @@ aliases:
   - /build/customize/bake/
 ---
 
-{{% experimental %}}
-
-Bake is an experimental feature, and we are looking for
-[feedback from users](https://github.com/docker/buildx/issues).
-
-{{% /experimental %}}
-
 Bake is a feature of Docker Buildx that lets you define your build configuration
 using a declarative file, as opposed to specifying a complex CLI expression. It
 also lets you run multiple builds concurrently with a single invocation.

@@ -158,7 +158,7 @@ COPY . .
 CMD ["node", "app.js"]
 ```
 
-With this Dockerfile, you can use `--build-arg` to override the default value of `ENV`:
+With this Dockerfile, you can use `--build-arg` to override the default value of `NODE_ENV`:
 
 ```console
 $ docker build --build-arg NODE_ENV=development .

@@ -13,6 +13,37 @@ issues, and bug fixes in [Dockerfile reference](/reference/dockerfile.md).
 
 For usage, see the [Dockerfile frontend syntax](frontend.md) page.
 
+## 1.13.0
+
+{{< release-date date="2025-01-20" >}}
+
+The full release note for this release is available
+[on GitHub](https://github.com/moby/buildkit/releases/tag/dockerfile%2F1.13.0).
+
+```dockerfile
+# syntax=docker/dockerfile:1.13.0
+```
+
+- New `TARGETOSVERSION`, `BUILDOSVERSION` builtin build-args are available for Windows builds, and `TARGETPLATFORM` value now also contains `OSVersion` value. [moby/buildkit#5614](https://github.com/moby/buildkit/pull/5614)
+- Allow syntax forwarding for external frontends for files starting with a Byte Order Mark (BOM). [moby/buildkit#5645](https://github.com/moby/buildkit/pull/5645)
+- Default `PATH` in Windows Containers has been updated with `powershell.exe` directory. [moby/buildkit#5446](https://github.com/moby/buildkit/pull/5446)
+- Fix Dockerfile directive parsing to not allow invalid syntax. [moby/buildkit#5646](https://github.com/moby/buildkit/pull/5646)
+- Fix case where `ONBUILD` command may have run twice on inherited stage. [moby/buildkit#5593](https://github.com/moby/buildkit/pull/5593)
+- Fix possible missing named context replacement for child stages in Dockerfile. [moby/buildkit#5596](https://github.com/moby/buildkit/pull/5596)
+
+## 1.13.0-labs
+
+{{< release-date date="2025-01-20" >}}
+
+The full release note for this release is available
+[on GitHub](https://github.com/moby/buildkit/releases/tag/dockerfile%2F1.13.0-labs).
+
+```dockerfile
+# syntax=docker.io/docker/dockerfile-upstream:1.13.0-labs
+```
+
+- Fix support for non-octal values for `COPY --chmod`. [moby/buildkit#5626](https://github.com/moby/buildkit/pull/5626)
+
 ## 1.12.0
 
 {{< release-date date="2024-11-27" >}}

@@ -10,6 +10,38 @@ toc_max: 2
 This page contains information about the new features, improvements, and bug
 fixes in [Docker Buildx](https://github.com/docker/buildx).
 
+## 0.20.0
+
+{{< release-date date="2025-01-20" >}}
+
+The full release note for this release is available
+[on GitHub](https://github.com/docker/buildx/releases/tag/v0.20.0).
+
+### New
+
+- New `buildx history` command has been added that allows working with build records of completed and running builds. You can use these commands to list, inspect, remove your builds, replay the logs of already completed builds, and quickly open your builds in Docker Desktop Build UI for further debugging. This is an early version of this command and we expect to add more features in the future releases. [#2891](https://github.com/docker/buildx/pull/2891), [#2925](https://github.com/docker/buildx/pull/2925)
+
+### Enhancements
+
+- Bake: Definition now supports new object notation for the fields that previously required CSV strings as inputs (`attest`, `output`, `cache-from`, `cache-to`, `secret`, `ssh`). [docker/buildx#2758](https://github.com/docker/buildx/pull/2758), [docker/buildx#2848](https://github.com/docker/buildx/pull/2848), [docker/buildx#2871](https://github.com/docker/buildx/pull/2871), [docker/buildx#2814](https://github.com/docker/buildx/pull/2814)
+- Bake: Filesystem entitlements now error by default. To disable this behavior, you can set `BUILDX_BAKE_ENTITLEMENTS_FS=0`. [docker/buildx#2875](https://github.com/docker/buildx/pull/2875)
+- Bake: Infer Git authentication token from remote files to build request. [docker/buildx#2905](https://github.com/docker/buildx/pull/2905)
+- Bake: Add support for `--list` flag to list targets and variables. [docker/buildx#2900](https://github.com/docker/buildx/pull/2900), [docker/buildx#2907](https://github.com/docker/buildx/pull/2907)
+- Bake: Update lookup order for default definition files to load the files with "override" suffix later. [docker/buildx#2886](https://github.com/docker/buildx/pull/2886)
+
+### Bug fixes
+
+- Bake: Fix entitlements check for default SSH socket. [docker/buildx#2898](https://github.com/docker/buildx/pull/2898)
+- Bake: Fix missing default target in group's default targets. [docker/buildx#2863](https://github.com/docker/buildx/pull/2863)
+- Bake: Fix named context from target platform matching. [docker/buildx#2877](https://github.com/docker/buildx/pull/2877)
+- Fix missing documentation for quiet progress mode. [docker/buildx#2899](https://github.com/docker/buildx/pull/2899)
+- Fix missing last progress from loading layers. [docker/buildx#2876](https://github.com/docker/buildx/pull/2876)
+- Validate BuildKit configuration before creating a builder. [docker/buildx#2864](https://github.com/docker/buildx/pull/2864)
+
+### Packaging
+
+- Compose compatibility has been updated to v2.4.7. [docker/buildx#2893](https://github.com/docker/buildx/pull/2893), [docker/buildx#2857](https://github.com/docker/buildx/pull/2857), [docker/buildx#2829](https://github.com/docker/buildx/pull/2829)
+
 ## 0.19.1
 
 {{< release-date date="2024-11-27" >}}

@@ -9,44 +9,57 @@ aliases:
 weight: 60
 ---
 
-Docker Desktop includes a standalone Kubernetes server and client,
-as well as Docker CLI integration that runs on your machine. 
+Docker Desktop includes a standalone Kubernetes server and client, as well as Docker CLI integration, enabling local Kubernetes development and testing directly on your machine. 
 
-The Kubernetes server runs locally within your Docker instance, is not configurable, and is a single-node cluster. It runs within a Docker container on your local system, and
-is only for local testing. 
+The Kubernetes server runs as a single-node cluster within a Docker container. This lightweight setup helps you explore Kubernetes features, test workloads, and work with container orchestration in parallel with other Docker functionalities.
 
-Turning on Kubernetes allows you to deploy
-your workloads in parallel, on Kubernetes, Swarm, and as standalone containers. Turning on or off the Kubernetes server does not affect your other
-workloads.
+Kubernetes on Docker Desktop runs alongside other workloads, including Swarm services and standalone containers.
+
+## 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:
+
+- Generation of certificates and cluster configuration
+- Download and installation of Kubernetes internal components
+- Cluster bootup
+- Installation of additional controllers for networking and storage
+
+Turning the Kubernetes server on or off in Docker Desktop does not affect your other workloads.
 
 ## Install and turn on Kubernetes
 
-1. From the Docker Desktop Dashboard, select the **Settings**.
-2. Select **Kubernetes** from the left sidebar. 
-3. Next to **Enable Kubernetes**, select the checkbox.
-4. Select **Apply & Restart** to save the settings and then select **Install** to confirm. This instantiates images required to run the Kubernetes server as containers, and installs the `/usr/local/bin/kubectl` command on your machine.
+1. Open the Docker Desktop Dashboard and navigate to **Settings**.
+2. Select the **Kubernetes** tab. 
+3. Select the **Enable Kubernetes** checkbox.
+4. Select **Apply & Restart** to save the settings and then select **Install** to confirm. This sets up the images required to run the Kubernetes server as containers, and installs the `kubectl` command-line tool on your system at `/usr/local/bin/kubectl` (Mac) or `C:\Program Files\Docker\Docker\Resources\bin\kubectl.exe` (Windows).
 
-   > [!IMPORTANT]
+   > [!NOTE]
    >
-   > The `kubectl` binary is not automatically packaged with Docker Desktop for Linux. To install the kubectl command for Linux, see [Kubernetes documentation](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/). It should be installed at `/usr/local/bin/kubectl`.
+   > Docker Desktop for Linux does not include `kubectl` by default. You can install it separately by following the [Kubernetes installation guide](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/). Ensure the `kubectl` binary is installed at `/usr/local/bin/kubectl`.
 
-By default, Kubernetes containers are hidden from commands like `docker ps`, because managing them manually is not supported. Most users do not need this option. To see these internal containers, select **Show system containers (advanced)**. 
+When Kubernetes is enabled, its status is displayed in the Docker Desktop Dashboard footer and the Docker menu. 
 
-When Kubernetes is turned on and running, an additional status bar in the Docker Desktop Dashboard footer and Docker menu displays. 
+You can check which version of Kubernetes you're on with:
 
-> [!NOTE]
->
-> Docker Desktop does not upgrade your Kubernetes cluster automatically after a new update. To upgrade your Kubernetes cluster to the latest version, select **Reset Kubernetes Cluster**.
+```console
+$ kubectl version
+```
+
+### Viewing system containers
+
+By default, Kubernetes system containers are hidden. To inspect these containers, navigate to **Settings** > **Kubernetes** and then enable **Show system containers (advanced)**.
 
-## Use the kubectl command
+You can now view the running Kubernetes containers with `docker ps` or in the Docker Desktop Dashboard.
 
-Kubernetes integration provides the Kubernetes CLI command
+## Using the kubectl command
+
+Kubernetes integration automatically installs the Kubernetes CLI command
 at `/usr/local/bin/kubectl` on Mac and at `C:\Program Files\Docker\Docker\Resources\bin\kubectl.exe` on Windows. This location may not be in your shell's `PATH`
 variable, so you may need to type the full path of the command or add it to
 the `PATH`.
 
 If you have already installed `kubectl` and it is
-pointing to some other environment, such as `minikube` or a GKE cluster, ensure you change the context so that `kubectl` is pointing to `docker-desktop`:
+pointing to some other environment, such as `minikube` or a Google Kubernetes Engine cluster, ensure you change the context so that `kubectl` is pointing to `docker-desktop`:
 
 ```console
 $ kubectl config get-contexts
@@ -55,29 +68,46 @@ $ kubectl config use-context docker-desktop
 
 > [!TIP]
 >
-> Run the `kubectl` command in a CMD or PowerShell terminal, otherwise `kubectl config get-contexts` may return an empty result. 
->
-> If you are using a different terminal and this happens, you can try setting the `kubeconfig` environment variable to the location of the `.kube/config` file. 
+> If the `kubectl` config get-contexts command returns an empty result, try:
+> 
+> - Running the command in the Command Prompt or PowerShell.
+> - Setting the `KUBECONFIG` environment variable to point to your `.kube/config` file.
 
-If you installed `kubectl` using Homebrew, or by some other method, and
-experience conflicts, remove `/usr/local/bin/kubectl`.
+### Verify installation
 
-You can test the command by listing the available nodes:
+To confirm that Kubernetes is running, list the available nodes:
 
 ```console
 $ kubectl get nodes
-
 NAME                 STATUS    ROLES            AGE       VERSION
 docker-desktop       Ready     control-plane    3h        v1.29.1
 ```
 
+If you installed `kubectl` using Homebrew, or by some other method, and
+experience conflicts, remove `/usr/local/bin/kubectl`.
+
 For more information about `kubectl`, see the
 [`kubectl` documentation](https://kubernetes.io/docs/reference/kubectl/overview/).
 
+## Upgrade your cluster
+
+Kubernetes clusters are not automatically upgraded with Docker Desktop updates. To upgrade the cluster, you must manually select **Reset Kubernetes Cluster** in settings.
+
+## Troubleshooting
+
+- If Kubernetes fails to start, make sure Docker Desktop is running with enough allocated resources. Check **Settings** > **Resources**.
+- If the `kubectl` commands return errors, confirm the context is set to `docker-desktop`
+   ```console
+   $ kubectl config use-context docker-desktop
+   ```
+   You can then try checking the logs of the [Kubernetes system containers](#viewing-system-containers) if you have enabled that setting.
+- If you're experiencing cluster issues after updating, reset your Kubernetes cluster. Resetting a Kubernetes cluster can help resolve issues by essentially reverting the cluster to a clean state, and clearing out misconfigurations, corrupted data, or stuck resources that may be causing problems. If the issue still persists, you may need to clean and purge data, and then restart Docker Desktop. 
+
 ## Turn off and uninstall Kubernetes
 
 To turn off Kubernetes in Docker Desktop:
+
 1. From the Docker Desktop Dashboard, select the **Settings** icon.
-2. Select **Kubernetes** from the left sidebar. 
-3. Next to **Enable Kubernetes**, clear the checkbox
-4. Select **Apply & Restart** to save the settings.This stops and removes Kubernetes containers, and also removes the `/usr/local/bin/kubectl` command.
+2. Select the **Kubernetes** tab. 
+3. Deselect the **Enable Kubernetes** checkbox.
+4. Select **Apply & Restart** to save the settings. This stops and removes Kubernetes containers, and also removes the `/usr/local/bin/kubectl` command.
@@ -72,8 +72,8 @@ For more information on setting up WSL 2 with Docker Desktop, see [WSL](/manuals
 {{< /tab >}}
 {{< tab name="Hyper-V backend, x86_64" >}}
 
-- Windows 11 64-bit: Home or Pro version 22H2 or higher, or Enterprise or Education version 22H2 or higher.
-- Windows 10 64-bit: Minimum required is Home or Pro 22H2 (build 19045) or higher, or Enterprise or Education 22H2 (build 19045) or higher.
+- Windows 11 64-bit: Enterprise, Pro, or Education version 22H2 or higher.
+- Windows 10 64-bit: Enterprise, Pro, or Education version 22H2 (build 19045) or higher.
 - Turn on Hyper-V and Containers Windows features.
 - The following hardware prerequisites are required to successfully run Client
   Hyper-V on Windows 10:

@@ -0,0 +1,16 @@
+---
+datafolder: buildx
+datafile: docker_buildx_history
+title: docker buildx history
+layout: cli
+aliases:
+- /engine/reference/commandline/buildx_history/
+---
+
+<!--
+This page is automatically generated from Docker's source code. If you want to
+suggest a change to the text that appears here, open a ticket or pull request
+in the source repository on GitHub:
+
+https://github.com/docker/buildx
+-->
@@ -0,0 +1,16 @@
+---
+datafolder: buildx
+datafile: docker_buildx_history_inspect
+title: docker buildx history inspect
+layout: cli
+aliases:
+- /engine/reference/commandline/buildx_history_inspect/
+---
+
+<!--
+This page is automatically generated from Docker's source code. If you want to
+suggest a change to the text that appears here, open a ticket or pull request
+in the source repository on GitHub:
+
+https://github.com/docker/buildx
+-->