docker · dvdksn · Nov 14, 2024 · Oct 31, 2024 · Oct 31, 2024 · Nov 4, 2024
diff --git a/_vale/Docker/RecommendedWords.yml b/_vale/Docker/RecommendedWords.yml
@@ -14,7 +14,7 @@ swap:
   (?:sign on|log on|log in|logon|login): sign in
   above: previous
   adaptor: adapter
-  admin: administrator
+  admin(?! console): administrator
   administrate: administer
   afterwards: afterward
   allow: let

diff --git a/_vale/config/vocabularies/Docker/accept.txt b/_vale/config/vocabularies/Docker/accept.txt
@@ -1,5 +1,4 @@
 (?-i)[A-Z]{2,}s
-Admin Console
 Amazon
 Anchore
 Apple

diff --git a/content/get-started/docker-concepts/the-basics/what-is-a-registry.md b/content/get-started/docker-concepts/the-basics/what-is-a-registry.md
@@ -52,7 +52,7 @@ The following diagram shows the relationship between a registry, repositories, a
 +---------------------------------------+
 ```
 
->**Note**
+> [!NOTE]
 >
 > You can create one private repository and unlimited public repositories using the free version of Docker Hub. For more information, visit the [Docker Hub subscription page](https://www.docker.com/pricing/).
 
@@ -112,7 +112,7 @@ Don't worry about the specifics of the Dockerfile, as you'll learn about that in
     docker build -t <YOUR_DOCKER_USERNAME>/docker-quickstart .
     ```
 
-    >**Note**
+    > [!NOTE]
     >
     > Make sure you include the dot (.) at the end of the `docker build` command. This tells Docker where to find the Dockerfile.
 

diff --git a/content/get-started/workshop/03_updating_app.md b/content/get-started/workshop/03_updating_app.md
@@ -72,9 +72,9 @@ To remove a container, you first need to stop it. Once it has stopped, you can r
    $ docker rm <the-container-id>
    ```
 
->**Note**
+> [!NOTE]
 >
->You can stop and remove a container in a single command by adding the `force` flag to the `docker rm` command. For example: `docker rm -f <the-container-id>`
+> You can stop and remove a container in a single command by adding the `force` flag to the `docker rm` command. For example: `docker rm -f <the-container-id>`
 
 {{< /tab >}}
 {{< tab name="Docker Desktop" >}}

diff --git a/content/get-started/workshop/08_using_compose.md b/content/get-started/workshop/08_using_compose.md
@@ -268,12 +268,12 @@ quickly see what container is your app and which container is the mysql database
 When you're ready to tear it all down, simply run `docker compose down` or hit the trash can on the Docker Desktop Dashboard
 for the entire app. The containers will stop and the network will be removed.
 
->**Warning**
+> [!WARNING]
 >
->By default, named volumes in your compose file are not removed when you run `docker compose down`. If you want to
+> By default, named volumes in your compose file are not removed when you run `docker compose down`. If you want to
 >remove the volumes, you need to add the `--volumes` flag.
 >
->The Docker Desktop Dashboard does not remove volumes when you delete the app stack.
+> The Docker Desktop Dashboard does not remove volumes when you delete the app stack.
 
 ## Summary
 

diff --git a/content/includes/aci-ecs-eol.md b/content/includes/aci-ecs-eol.md
@@ -1,3 +1,3 @@
->**Important**
+> [!IMPORTANT]
 >
->Docker Compose's integration for ECS and ACI is retiring in November 2023.
+> Docker Compose's integration for ECS and ACI is retiring in November 2023.
diff --git a/content/includes/install-script.md b/content/includes/install-script.md
@@ -30,9 +30,9 @@ of the convenience script:
   using the script to update an existing installation, dependencies may not be
   updated to the expected version, resulting in outdated versions.
 
-> **Tip: preview script steps before running**
+> [!TIP]
 >
-> You can run the script with the `--dry-run` option to learn what steps the
+> Preview script steps before running. You can run the script with the `--dry-run` option to learn what steps the
 > script will run when invoked:
 >
 > ```console

@@ -93,14 +93,14 @@ multiple Dockerfiles that can't be easily merged into one.
 
 ## Deduplicate context transfer
 
-> **Note**
+> [!NOTE]
 >
-> As of Buildx version 0.17.0 and later, Bake automatically deduplicates
+> As of Buildx version 0.17.0 and later, Bake automatically de-duplicates
 > context transfer for targets that share the same context. In addition to
 > Buildx version 0.17.0, the builder must be running BuildKit version 0.16.0 or
 > later, and the Dockerfile syntax must be `docker/dockerfile:1.10` or later.
 >
-> If you meet these requirements, you don't need to manually deduplicate
+> If you meet these requirements, you don't need to manually de-duplicate
 > context transfer as described in this section.
 >
 > - To check your Buildx version, run `docker buildx version`.

@@ -19,13 +19,13 @@ Computing components of an application are defined as [services](/reference/comp
 
 Services communicate with each other through [networks](/reference/compose-file/networks.md). In the Compose Specification, a network is a platform capability abstraction to establish an IP route between containers within services connected together.
 
-Services store and share persistent data into [volumes](/reference/compose-file/volumes.md). The Specification describes such a persistent data as a high-level filesystem mount with global options. 
+Services store and share persistent data into [volumes](/reference/compose-file/volumes.md). The Specification describes such a persistent data as a high-level filesystem mount with global options.
 
 Some services require configuration data that is dependent on the runtime or platform. For this, the Specification defines a dedicated [configs](/reference/compose-file/configs.md) concept. From a service container point of view, configs are comparable to volumes, in that they are files mounted into the container. But the actual definition involves distinct platform resources and services, which are abstracted by this type.
 
 A [secret](/reference/compose-file/secrets.md) is a specific flavor of configuration data for sensitive data that should not be exposed without security considerations. Secrets are made available to services as files mounted into their containers, but the platform-specific resources to provide sensitive data are specific enough to deserve a distinct concept and definition within the Compose specification.
 
->**Note**
+> [!NOTE]
 >
 > With volumes, configs and secrets you can have a simple declaration at the top-level and then add more platform-specific information at the service level.
 

@@ -1004,9 +1004,9 @@ For the full change log or additional information, check the [Compose repository
 
 {{< release-date date="2022-09-27" >}}
 
-> [!NOTE]     
-> 
-> - Updates on environment file syntax & interpolation: see [compose#9879](https://github.com/docker/compose/issues/9879)  
+> [!NOTE]
+>
+> - Updates on environment file syntax & interpolation: see [compose#9879](https://github.com/docker/compose/issues/9879)
 > - Setting `DOCKER_HOST` via `.env` files is not supported in Compose v2
 
 ### Updates
@@ -1145,10 +1145,9 @@ For the full change log, check the [Compose repository 2.10.0 release page](http
 > [!IMPORTANT]
 >
 > Compose v2.9.0 contains changes to the environment variable's precedence that have since been reverted. We recommend using v2.10+ to avoid compatibility issues.
->
 
 > [!NOTE]
-> 
+>
 > This release reverts the breaking changes introduced in [Compose v2.8.0](#280) by [`compose-go v1.3.0`](https://github.com/compose-spec/compose-go/releases/tag/v1.3.0).
 
 ### Updates
@@ -1976,8 +1975,9 @@ This release contains minor improvements and bug fixes.
 
 - Reverted a 1.23.0 change that appended random strings to container names
   created by `docker-compose up`, causing addressability issues.
-  > [!NOTE]: Containers created by `docker-compose run` will continue to use
-  randomly generated names to avoid collisions during parallel runs.
+  > [!NOTE]
+  >
+  > Containers created by `docker-compose run` will continue to use randomly generated names to avoid collisions during parallel runs.
 
 - Fixed an issue where some `dockerfile` paths would fail unexpectedly when
   attempting to build on Windows.
@@ -2981,7 +2981,10 @@ naming scheme accordingly before upgrading.
 - Containers dependencies can now be set up to wait on positive healthchecks
   when declared using `depends_on`. See the documentation for the updated
   syntax.
-  **Note**: This feature will not be ported to version 3 Compose files.
+
+  > [!NOTE]
+  >
+  > This feature will not be ported to version 3 Compose files.
 
 - Added support for the `sysctls` parameter in service definitions
 

@@ -1450,7 +1450,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 36 Release Notes (2017-01-12 1.13.0-rc6-beta36)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1464,7 +1466,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 35 Release Notes (2017-01-06 1.13.0-rc5-beta35)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1475,7 +1479,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 34.1 Release Notes (2016-12-22 1.13.0-rc4-beta34.1)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Hotfix**
 
@@ -1487,7 +1493,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 34 Release Notes (2016-12-20 1.13.0-rc4-beta34)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 
@@ -1509,15 +1517,19 @@ TCP connection is idle for more than five minutes (related to
 
 ### Beta 33.1 Release Notes (2016-12-16 1.13.0-rc3-beta33.1)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Hotfix**
 
 - Fixed issue where sometimes TRIM would cause the virtual machine to hang
 
 ### Beta 33 Release Notes (2016-12-15 1.13.0-rc3-beta33)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 
@@ -1926,7 +1938,9 @@ events or unexpected unmounts.
 
 ### Beta 18.1 Release Notes (2016-07-07 1.12.0-rc3-beta18.1)
 
->**Note**: Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
+> [!NOTE]
+>
+> Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
 
 **Hotfix**
 

@@ -1276,9 +1276,10 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
 TCP connection is idle for more than 5 minutes (related to
 [docker/for-mac#1374](https://github.com/docker/for-mac/issues/1374))
 
-> [!NOTE]: The link above goes to Docker for Mac issues because a
-Mac user reported this problem, which applied to both Mac and Windows
-and was fixed on both.
+> [!NOTE]
+>
+> The link above goes to Docker for Mac issues because a
+Mac user reported this problem, which applied to both Mac and Windows and was fixed on both.
 
 ### Docker Community Edition 17.07.0-rc3-win23 Release Notes (2017-08-21 17.07.0-win23)
 
@@ -1626,7 +1627,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 36 Release Notes (2017-01-12 1.13.0-rc6-beta36)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1640,7 +1643,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 35 Release Notes (2017-01-06 1.13.0-rc5-beta35)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Upgrades**
 
@@ -1669,7 +1674,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 33 Release Notes (2016-12-15 1.13.0-rc3-beta33)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 
@@ -1686,7 +1693,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 32.1 Release Notes (2016-12-09 1.13.0-rc3-beta32.1)
 
->**Important Note:** Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> [!IMPORTANT]
+>
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **Hotfixes**
 
@@ -1716,9 +1725,9 @@ registry access (fixes [docker/for-win#569](https://github.com/docker/for-win/is
 
 ### Beta 32 Release Notes (2016-12-07 1.13.0-rc3-beta32)
 
->**Important Note**:
+> [!IMPORTANT]
 >
->  Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
+> Plugins installed using the experimental "managed plugins" feature in Docker 1.12 must be removed/uninstalled before upgrading.
 
 **New**
 
@@ -2070,7 +2079,9 @@ Unreleased. See Beta 23 for changes.
 
 ### Beta 18.1 Release (2016-07-07 1.12.0-rc3-beta18.1)
 
->**Note**: Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
+> [!NOTE]
+>
+> Docker 1.12.0 RC3 release introduces a backward incompatible change from RC2. You can fix this by recreating or updating your containers.
 
 **Hotfix**
 
@@ -2493,7 +2504,9 @@ are working on a solution.
 * Fix msi version
 * Don't truncate Toolbox link
 
->**Note**: Docker for Windows skipped from Beta 1 to Beta 5 at this point to synch up the version numbering with Docker for Mac, which went into beta cycles a little earlier.
+> [!NOTE]
+>
+> Docker for Windows skipped from Beta 1 to Beta 5 at this point to synch up the version numbering with Docker for Mac, which went into beta cycles a little earlier.
 
 ### Beta 1 Release (2016-03-24 1.10.6)
 

@@ -25,7 +25,7 @@ This page contains information on how to install, launch and upgrade Docker Desk
 To install Docker Desktop successfully, you must:
 
 - Meet the [general system requirements](_index.md#general-system-requirements).
-- Have a 64-bit version of Fedora 39 or Fedora 40.
+- Have a 64-bit version of Fedora 40 or Fedora 41.
 
 Additionally, for a GNOME desktop environment you must install AppIndicator and KStatusNotifierItem [GNOME extensions](https://extensions.gnome.org/extension/615/appindicator-support/).
 

@@ -161,7 +161,7 @@ again when you switch back.
 
 > [!TIP]
 >
-> See the [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md#how-do-I-run-docker-desktop-without-administrator-privileges) on how to install and run Docker Desktop without needing administrator privileges.
+> See the [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md#how-do-i-run-docker-desktop-without-administrator-privileges) on how to install and run Docker Desktop without needing administrator privileges.
 
 ### Install interactively
 

@@ -67,7 +67,7 @@ To move the disk image file to a different location:
 
 3. Select **Apply & Restart** for the changes to take effect.
 
->**Important**
+> [!IMPORTANT]
 >
 > Do not move the file directly in Finder as this can cause Docker Desktop to lose track of the file.
 

@@ -10,8 +10,7 @@ aliases:
 
 > [!NOTE]
 >
-> Automated builds require a
-> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
+> Automated builds require a [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
 
 To automate building and testing of your images, you link to your hosted source
 code service to Docker Hub so that it can access your source code
@@ -38,7 +37,7 @@ If you are linking a source code provider to create autobuilds for a team, follo
 
     ![Granting access to GitHub account](images/authorize-builder.png)
 
-    >**Note**
+    > [!NOTE]
     >
     > If you are the owner of any GitHub organizations, you might see
     options to grant Docker Hub access to them from this screen. You can also