Merge pull request #21931 from docker/published-update

publish updates from main

Author: aevesdocker

_vale/config/vocabularies/Docker/accept.txt

@@ -57,6 +57,7 @@ Jamf
 JetBrains
 Kerberos
 Kitematic
+Kubeadm
 Kubernetes
 Laravel
 Laradock

content/contribute/components/call-outs.md

@@ -6,18 +6,25 @@ toc_max: 3
 
 We support these broad categories of callouts:
 
-- Alerts (Note, Tip, Important, Warning, Caution)
-- Version callouts
-- Experimental, which use the `{{%/* experimental */%}}` shortcode
-- Restricted, which use the `{{%/* restricted */%}}` shortcode
+- Alerts: Note, Tip, Important, Warning, Caution
 
-The experimental and restricted shortcodes take a title as an argument. The
-title is optional, defaults to "Experimental" or "Restricted" respectively, and
-is displayed in the callout.
+We also support summary bars, which represent a feature's required subscription, version, or Adminstrator role.
+To add a summary bar:
+
+Add the feature name to the `/data/summary.yaml` file. Use the following attributes:
+
+| Attribute      | Description                                            | Possible values                                         |
+|----------------|--------------------------------------------------------|---------------------------------------------------------|
+| `subscription` | Notes the subscription required to use the feature     | All, Personal, Pro, Team, Business                      |
+| `availability` | Notes what product development stage the feature is in | Experimental, Beta, Early access, GA, Retired           |
+| `requires`     | Notes what minimum version is required for the feature | No specific value, use a string to describe the version and link to relevant release notes |
+| `for`          | Notes if the feature is intended for IT Administrators | Administrators                                          |
+
+Then, add the `summary-bar` shortcode on the page you want to add the summary bar to. Note, the feature name is case sensitive. The icons that appear in the summary bar are automatically rendered.
 
 ## Examples
 
-{{< introduced buildx 0.16.0 >}}
+{{< summary-bar feature_name="PKG installer" >}}
 
 > [!NOTE]
 >
@@ -54,18 +61,10 @@ is displayed in the callout.
 
 For both of the following callouts, consult [the Docker release lifecycle](/release-lifecycle) for more information on when to use them.
 
-{{% experimental title="Beta feature" %}}
-The Builds view is currently in Beta. This feature may change or be removed from future releases.
-{{% /experimental %}}
-
-{{% restricted %}}
-Docker Scout is an [early access](/release-lifecycle/#early-access-ea) product.
-{{% /restricted %}}
-
-## Formatting 
+## Formatting
 
 ```go
-{{</* introduced buildx 0.10.4 "../../release-notes.md#0104" */>}}
+> {{< summary-bar feature_name="PKG installer" >}}
 ```
 
 ```html
@@ -101,14 +100,4 @@ Docker Scout is an [early access](/release-lifecycle/#early-access-ea) product.
 > [!CAUTION]
 >
 > Here be dragons.
-```
-
-```go
-{{%/* experimental title="Beta feature" */%}}
-The Builds view is currently in Beta. This feature may change or be removed from future releases.
-{{%/* /experimental */%}}
-
-{{%/* restricted */%}}
-Docker Scout is an [early access](/release-lifecycle/#early-access-ea) product.
-{{%/* /restricted */%}}
-```
+```

content/manuals/build/builders/drivers/_index.md

@@ -66,7 +66,7 @@ To build an image using a non-default driver and load it to the image store,
 
 ### Load by default
 
-{{< introduced buildx 0.14.0 >}}
+{{< summary-bar feature_name="Load by default" >}}
 
 You can configure the custom build drivers to behave in a similar way to the
 default `docker` driver, and load images to the local image store by default.

content/manuals/build/building/variables.md

@@ -352,7 +352,7 @@ Setting `NO_COLOR` to anything turns off colorized output, as recommended by
 
 ### BUILDKIT_HOST
 
-{{< introduced buildx 0.9.0 "../release-notes.md#090" >}}
+{{< summary-bar feature_name="Buildkit host" >}}
 
 You use the `BUILDKIT_HOST` to specify the address of a BuildKit daemon to use
 as a remote builder. This is the same as specifying the address as a positional
@@ -438,7 +438,7 @@ Example:
 
 ### BUILDX_BAKE_GIT_AUTH_HEADER
 
-{{< introduced buildx 0.14.0 >}}
+{{< summary-bar feature_name="Buildx bake Git auth token" >}}
 
 Sets the HTTP authentication scheme when using a remote Bake definition in a private Git repository.
 This is equivalent to the [`GIT_AUTH_HEADER` secret](./secrets#http-authentication-scheme),
@@ -453,7 +453,7 @@ $ export BUILDX_BAKE_GIT_AUTH_HEADER=basic
 
 ### BUILDX_BAKE_GIT_AUTH_TOKEN
 
-{{< introduced buildx 0.14.0 >}}
+{{< summary-bar feature_name="Buildx bake Git auth token" >}}
 
 Sets the HTTP authentication token when using a remote Bake definition in a private Git repository.
 This is equivalent to the [`GIT_AUTH_TOKEN` secret](./secrets#git-authentication-for-remote-contexts),
@@ -467,7 +467,7 @@ $ export BUILDX_BAKE_GIT_AUTH_TOKEN=$(cat git-token.txt)
 
 ### BUILDX_BAKE_GIT_SSH
 
-{{< introduced buildx 0.14.0 >}}
+{{< summary-bar feature_name="Buildx bake Git SSH" >}}
 
 Lets you specify a list of SSH agent socket filepaths to forward to Bake
 for authenticating to a Git server when using a remote Bake definition in a private repository.
@@ -512,7 +512,7 @@ $ export BUILDX_CONFIG=/usr/local/etc
 
 ### BUILDX_CPU_PROFILE
 
-{{< introduced buildx 0.18.0 >}}
+{{< summary-bar feature_name="Buildx CPU profile" >}}
 
 If specified, Buildx generates a `pprof` CPU profile at the specified location.
 
@@ -538,7 +538,7 @@ $ export BUILDX_EXPERIMENTAL=1
 
 ### BUILDX_GIT_CHECK_DIRTY
 
-{{< introduced buildx 0.10.4 "../release-notes.md#0104" >}}
+{{< summary-bar feature_name="Buildx Git check dirty" >}}
 
 When set to true, checks for dirty state in source control information for
 [provenance attestations](/manuals/build/metadata/attestations/slsa-provenance.md).
@@ -551,7 +551,7 @@ $ export BUILDX_GIT_CHECK_DIRTY=1
 
 ### BUILDX_GIT_INFO
 
-{{< introduced buildx 0.10.0 "../release-notes.md#0100" >}}
+{{< summary-bar feature_name="Buildx Git info" >}}
 
 When set to false, removes source control information from
 [provenance attestations](/manuals/build/metadata/attestations/slsa-provenance.md).
@@ -564,7 +564,7 @@ $ export BUILDX_GIT_INFO=0
 
 ### BUILDX_GIT_LABELS
 
-{{< introduced buildx 0.10.0 "../release-notes.md#0100" >}}
+{{< summary-bar feature_name="Buildx Git labels" >}}
 
 Adds provenance labels, based on Git information, to images that you build. The
 labels are:
@@ -593,7 +593,7 @@ If the repository is in a dirty state, the `revision` gets a `-dirty` suffix.
 
 ### BUILDX_MEM_PROFILE
 
-{{< introduced buildx 0.18.0 >}}
+{{< summary-bar feature_name="Buildx mem profile" >}}
 
 If specified, Buildx generates a `pprof` memory profile at the specified
 location.
@@ -610,7 +610,7 @@ $ export BUILDX_MEM_PROFILE=buildx_mem.prof
 
 ### BUILDX_NO_DEFAULT_ATTESTATIONS
 
-{{< introduced buildx 0.10.4 "../release-notes.md#0104" >}}
+{{< summary-bar feature_name="Buildx no default" >}}
 
 By default, BuildKit v0.11 and later adds
 [provenance attestations](/manuals/build/metadata/attestations/slsa-provenance.md) to images you

content/manuals/build/exporters/_index.md

@@ -184,7 +184,7 @@ WARNING: No output specified with docker-container driver.
 
 ## Multiple exporters
 
-{{< introduced buildx 0.13.0 >}}
+{{< summary-bar feature_name="Build multiple exporters" >}}
 
 You can use multiple exporters for any given build by specifying the `--output`
 flag multiple times. This requires **both Buildx and BuildKit** version 0.13.0

content/manuals/compose/how-tos/environment-variables/envvars.md

@@ -172,7 +172,7 @@ If `COMPOSE_ENV_FILES` is not set, and you don't provide `--env-file` in the CLI
 
 ### COMPOSE\_MENU
 
-{{< introduced compose 2.26.0 "/manuals/compose/releases/release-notes.md#2260" >}}
+{{< summary-bar feature_name="Compose menu" >}}
 
 When enabled, Compose displays a navigation menu where you can choose to open the Compose stack in Docker Desktop, switch on [`watch` mode](../file-watch.md), or use [Docker Debug](/reference/cli/docker/debug.md).
 
@@ -183,7 +183,7 @@ When enabled, Compose displays a navigation menu where you can choose to open th
 
 ### COMPOSE\_EXPERIMENTAL
 
-{{< introduced compose 2.26.0 "/manuals/compose/releases/release-notes.md#2260" >}}
+{{< summary-bar feature_name="Compose experimental" >}}
 
 This is an opt-out variable. When turned off it deactivates the experimental features such as the navigation menu or [Synchronized file shares](/manuals/desktop/features/synchronized-file-sharing.md).
 

content/manuals/compose/how-tos/file-watch.md

@@ -7,7 +7,7 @@ aliases:
 - /compose/file-watch/
 ---
 
-{{< introduced compose 2.22.0 "/manuals/compose/releases/release-notes.md#2220" >}}
+{{< summary-bar feature_name="Compose file watch" >}}
 
 {{% include "compose/watch.md" %}}
 

content/manuals/compose/how-tos/lifecycle.md

@@ -6,7 +6,7 @@ desription: How to use lifecycle hooks with Docker Compose
 keywords: cli, compose, lifecycle, hooks reference
 ---
 
-{{< introduced compose 2.30.0 "../releases/release-notes.md#2300" >}}
+{{< summary-bar feature_name="Compose lifecycle hooks" >}}
 
 ## Services lifecycle hooks
 

content/manuals/compose/how-tos/multiple-compose-files/include.md

@@ -6,7 +6,7 @@ aliases:
 - /compose/multiple-compose-files/include/
 ---
 
-{{< introduced compose 2.20.3 "/manuals/compose/releases/release-notes.md#2203" >}}
+{{< summary-bar feature_name="Compose include" >}}
 
 {{% include "compose/include.md" %}}
 

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. It is available with Docker Desktop version 4.37 and later.
+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 provides:
 
@@ -35,6 +35,8 @@ docker desktop COMMAND [OPTIONS]
 | `restart`            | Restarts Docker Desktop                  |
 | `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) |
+| `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. |
+
 
 For more details on each command, see the [Docker Desktop CLI reference](/reference/cli/docker/desktop/_index.md).