Merge pull request #21403 from sarahsanders-docker/ENGDOCS-2281

Clean up callout PR

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.
 

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" >}}

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
 

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.

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

content/manuals/build/bake/contexts.md

@@ -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`.

content/manuals/compose/intro/compose-application-model.md

@@ -25,7 +25,7 @@ Some services require configuration data that is dependent on the runtime or pla
 
 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.
 

content/manuals/compose/releases/release-notes.md

@@ -1145,7 +1145,6 @@ 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]
 >
@@ -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
+  > [!NOTE]
-  randomly generated names to avoid collisions during parallel runs.
+  >
+  > 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
 

content/manuals/desktop/previous-versions/edge-releases-mac.md

@@ -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,7 +1517,9 @@ 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**
 
@@ -1517,7 +1527,9 @@ TCP connection is idle for more than five minutes (related to
 
 ### 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**
 

content/manuals/desktop/previous-versions/edge-releases-windows.md

@@ -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
+> [!NOTE]
-Mac user reported this problem, which applied to both Mac and Windows
+>
-and was fixed on both.
+> 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)
 

content/manuals/desktop/troubleshoot-and-support/faqs/macfaqs.md

@@ -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.
 

content/manuals/docker-hub/builds/link-source.md

@@ -10,8 +10,7 @@ aliases:
 
 > [!NOTE]
 >
-> Automated builds require a
+> Automated builds require a [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
-> [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

content/manuals/docker-hub/builds/manage-builds.md

@@ -6,8 +6,7 @@ keywords: autobuilds, automated, docker hub, registry
 
 > [!NOTE]
 >
-> Automated builds require a
+> Automated builds require a [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
-> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
 
 ## Cancel or retry a build
 
@@ -32,11 +31,9 @@ From either location, you can select a build job to view its build report. The
 build report shows information about the build job. This includes the source
 repository and branch, or tag, the build logs, the build duration, creation time and location, and the user account the build occurred in.
 
->**Note**
+> [!NOTE]
 >
-> You can now view the progress of your builds every 30 seconds when you
+> You can now view the progress of your builds every 30 seconds when you refresh the **Builds** page. With the in-progress build logs, you can debug your builds before they're finished.
-> refresh the **Builds** page. With the in-progress build logs, you can debug your
-> builds before they're finished.
 
 ![Build report](/docker-hub/images/index-report.png)
 

content/manuals/docker-hub/download-rate-limit.md

@@ -213,7 +213,7 @@ docker-ratelimit-source
 
 These headers are returned on both GET and HEAD requests.
 
->**Note**
+> [!NOTE]
 >
 > Using GET emulates a real pull and counts towards the limit. Using HEAD won't.
 > To check your limits, you need `curl`, `grep`, and `jq` installed.

content/manuals/docker-hub/quickstart.md

@@ -172,6 +172,10 @@ customize your own images to suit specific needs.
    $ docker push <YOUR-USERNAME>/nginx-custom
    ```
 
+    > [!NOTE]
+    >
+    > You must be signed in to Docker Hub through Docker Desktop or the command line, and you must also name your images correctly, as per the above steps.
+
    The command pushes the image to Docker Hub and automatically
    creates the repository if it doesn't exist. To learn more about the command,
    see the [`docker push` CLI

content/manuals/engine/logging/configure.md

@@ -22,9 +22,9 @@ As a default, Docker uses the [`json-file` logging driver](drivers/json-file.md)
 caches container logs as JSON internally. In addition to using the logging drivers
 included with Docker, you can also implement and use [logging driver plugins](plugins.md).
 
-> **Tip: use the `local` logging driver to prevent disk-exhaustion**
+> [!TIP]
 >
-> By default, no log-rotation is performed. As a result, log-files stored by the
+> Use the `local` logging driver to prevent disk-exhaustion. By default, no log-rotation is performed. As a result, log-files stored by the
 > default [`json-file` logging driver](drivers/json-file.md) logging driver can cause
 > a significant amount of disk space to be used for containers that generate much
 > output, which can lead to disk space exhaustion.

content/manuals/engine/network/links.md

@@ -9,9 +9,9 @@ aliases:
 - /network/links/
 ---
 
->**Warning**
+> [!WARNING]
 >
->The `--link` flag is a legacy feature of Docker. It may eventually
+> The `--link` flag is a legacy feature of Docker. It may eventually
 be removed. Unless you absolutely need to continue using it, we recommend that you use
 user-defined networks to facilitate communication between two containers instead of using
 `--link`. One feature that user-defined networks do not support that you can do

content/manuals/engine/release-notes/17.03.md

@@ -71,13 +71,9 @@ toc_max: 2
 ## 17.03.0-ce
 2017-03-01
 
-**IMPORTANT**: Starting with this release, Docker is on a monthly release cycle and uses a
+> [!IMPORTANT]
-new YY.MM versioning scheme to reflect this. Two channels are available: monthly and quarterly.
+>
-Any given monthly release will only receive security and bugfixes until the next monthly
+> Starting with this release, Docker is on a monthly release cycle and uses a new YY.MM versioning scheme to reflect this. Two channels are available: monthly and quarterly. Any given monthly release will only receive security and bugfixes until the next monthly release is available. Quarterly releases receive security and bugfixes for 4 months after initial release. This release includes bugfixes for 1.13.1 but there are no major feature additions and the API version stays the same. Upgrading from Docker 1.13.1 to 17.03.0 is expected to be simple and low-risk.
-release is available. Quarterly releases receive security and bugfixes for 4 months after
-initial release. This release includes bugfixes for 1.13.1 but
-there are no major feature additions and the API version stays the same.
-Upgrading from Docker 1.13.1 to 17.03.0 is expected to be simple and low-risk.
 
 ### Client
 

content/manuals/engine/release-notes/20.10.md

@@ -399,15 +399,9 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
 ## 20.10.11
 2021-11-17
 
-> **IMPORTANT**
+> [!IMPORTANT]
 >
-> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
+> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to [Configure the daemon to use a proxy](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
-> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
-> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
-> environment variable for handling requests to `https://` URLs.
->
-> Refer to [Configure the daemon to use a proxy](/manuals/engine/daemon/proxy.md)
-> to learn how to configure the Docker Daemon to use a proxy server.
 
 
 ### Distribution
@@ -428,15 +422,9 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
 ## 20.10.10
 2021-10-25
 
-> **IMPORTANT**
+> [!IMPORTANT]
 >
-> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
+> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
-> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
-> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
-> environment variable for handling requests to `https://` URLs.
->
-> Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md)
-> to learn how to configure the Docker Daemon to use a proxy server.
 
 
 ### Builder
@@ -468,15 +456,9 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
 This release is a security release with security fixes in the CLI, runtime, as
 well as updated versions of the containerd.io package.
 
-> **IMPORTANT**
+> [!IMPORTANT]
 >
-> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
+> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
-> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
-> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
-> environment variable for handling requests to `https://` URLs.
->
-> Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md)
-> to learn how to configure the Docker Daemon to use a proxy server.
 
 ### Client
 
@@ -512,15 +494,9 @@ well as updated versions of the containerd.io package.
 ## 20.10.8
 2021-08-03
 
-> **IMPORTANT**
+> [!IMPORTANT]
 >
-> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http),
+> Due to [net/http changes](https://github.com/golang/go/issues/40909) in [Go 1.16](https://golang.org/doc/go1.16#net/http), HTTP proxies configured through the `$HTTP_PROXY` environment variable are no longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY` environment variable for handling requests to `https://` URLs. Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md) to learn how to configure the Docker Daemon to use a proxy server.
-> HTTP proxies configured through the `$HTTP_PROXY` environment variable are no
-> longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
-> environment variable for handling requests to `https://` URLs.
->
-> Refer to the [HTTP/HTTPS proxy section](/manuals/engine/daemon/proxy.md)
-> to learn how to configure the Docker Daemon to use a proxy server.
 
 ### Deprecation
 

content/manuals/engine/release-notes/prior-releases.md

@@ -16,15 +16,13 @@ aliases:
 
 ## 1.13.1 (2017-02-08)
 
-**Important**: On Linux distributions where `devicemapper` was the default storage driver,
+> [!IMPORTANT]
-the `overlay2`, or `overlay` is now used by default (if the kernel supports it).
+>
-To use devicemapper, you can manually configure the storage driver to use through
+> On Linux distributions where `devicemapper` was the default storage driver, the `overlay2`, or `overlay` is now used by default (if the kernel supports it). To use devicemapper, you can manually configure the storage driver to use through the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json` configuration file.
-the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json`
-configuration file.
 
-**Important**: In Docker 1.13, the managed plugin api changed, as compared to the experimental
+> [!IMPORTANT]
-version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12
+>
-_before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
+> In Docker 1.13, the managed plugin api changed, as compared to the experimental version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12 _before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
 
 If you have already upgraded to Docker 1.13 without uninstalling
 previously-installed plugins, you may see this message when the Docker daemon
@@ -66,15 +64,13 @@ To manually remove all plugins and resolve this problem, take the following step
 
 ## 1.13.0 (2017-01-18)
 
-**Important**: On Linux distributions where `devicemapper` was the default storage driver,
+> [!IMPORTANT]
-the `overlay2`, or `overlay` is now used by default (if the kernel supports it).
+>
-To use devicemapper, you can manually configure the storage driver to use through
+> On Linux distributions where `devicemapper` was the default storage driver, the `overlay2`, or `overlay` is now used by default (if the kernel supports it). To use devicemapper, you can manually configure the storage driver to use through the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json` configuration file.
-the `--storage-driver` daemon option, or by setting "storage-driver" in the `daemon.json`
-configuration file.
 
-**Important**: In Docker 1.13, the managed plugin api changed, as compared to the experimental
+> [!IMPORTANT]
-version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12
+>
-_before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
+> In Docker 1.13, the managed plugin api changed, as compared to the experimental version introduced in Docker 1.12. You must **uninstall** plugins which you installed with Docker 1.12 _before_ upgrading to Docker 1.13. You can uninstall plugins using the `docker plugin rm` command.
 
 If you have already upgraded to Docker 1.13 without uninstalling
 previously-installed plugins, you may see this message when the Docker daemon
@@ -299,16 +295,14 @@ To manually remove all plugins and resolve this problem, take the following step
 
 ## 1.12.6 (2017-01-10)
 
-**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
+> [!IMPORTANT]
-based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
+>
-upgrading from an older version of docker, the upgrade process may not
+> Docker 1.12 ships with an updated systemd unit file for rpm
-automatically install the updated version of the unit file, or fail to start
+based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
-the docker service if;
+> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
 
-- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+Starting the `docker service` will produce an error:
-- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
-
-Starting the docker service will produce an error:
 
     Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
 
@@ -326,8 +320,9 @@ To resolve this:
 After making those changes, run `sudo systemctl daemon-reload`, and `sudo
 systemctl restart docker` to reload changes and (re)start the docker daemon.
 
-**NOTE**: Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or
+> [!NOTE]
-that the IPAM driver can provide one when you specify the `--ipv6` option.
+>
+> Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or that the IPAM driver can provide one when you specify the `--ipv6` option.
 
 If you are currently using the `--ipv6` option _without_ specifying the
 `--fixed-cidr-v6` option, the Docker daemon will refuse to start with the
@@ -369,16 +364,14 @@ which supports automatic allocation of IPv6 subnets.
 
 ## 1.12.5 (2016-12-15)
 
-**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
+> [!IMPORTANT]
-based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
+>
-upgrading from an older version of docker, the upgrade process may not
+> Docker 1.12 ships with an updated systemd unit file for rpm
-automatically install the updated version of the unit file, or fail to start
+based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
-the docker service if;
+> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
 
-- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+Starting the `docker service` will produce an error:
-- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
-
-Starting the docker service will produce an error:
 
     Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
 
@@ -396,8 +389,9 @@ To resolve this:
 After making those changes, run `sudo systemctl daemon-reload`, and `sudo
 systemctl restart docker` to reload changes and (re)start the docker daemon.
 
-**NOTE**: Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or
+> [!NOTE]
-that the IPAM driver can provide one when you specify the `--ipv6` option.
+>
+> Docker 1.12.5 will correctly validate that either an IPv6 subnet is provided or that the IPAM driver can provide one when you specify the `--ipv6` option.
 
 If you are currently using the `--ipv6` option _without_ specifying the
 `--fixed-cidr-v6` option, the Docker daemon will refuse to start with the
@@ -447,16 +441,14 @@ which supports automatic allocation of IPv6 subnets.
 
 ## 1.12.4 (2016-12-12)
 
-**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
+> [!IMPORTANT]
-based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
+>
-upgrading from an older version of docker, the upgrade process may not
+> Docker 1.12 ships with an updated systemd unit file for rpm
-automatically install the updated version of the unit file, or fail to start
+based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
-the docker service if;
+> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
 
-- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+Starting the `docker service` will produce an error:
-- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
-
-Starting the docker service will produce an error:
 
     Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
 
@@ -522,16 +514,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
 
 ## 1.12.3 (2016-10-26)
 
-**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
+> [!IMPORTANT]
-based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
+>
-upgrading from an older version of docker, the upgrade process may not
+> Docker 1.12 ships with an updated systemd unit file for rpm
-automatically install the updated version of the unit file, or fail to start
+based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the Docker service if;
-the docker service if;
+> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
 
-- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+Starting the `docker service` will produce an error:
-- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
-
-Starting the docker service will produce an error:
 
     Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
 
@@ -589,16 +579,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
 
 ## 1.12.2 (2016-10-11)
 
-**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
+> [!IMPORTANT]
-based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
+>
-upgrading from an older version of docker, the upgrade process may not
+> Docker 1.12 ships with an updated systemd unit file for rpm
-automatically install the updated version of the unit file, or fail to start
+based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
-the docker service if;
+> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
 
-- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+Starting the `docker service` will produce an error:
-- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
-
-Starting the docker service will produce an error:
 
     Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
 
@@ -663,16 +651,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
 
 ## 1.12.1 (2016-08-18)
 
-**IMPORTANT**: Docker 1.12 ships with an updated systemd unit file for rpm
+> [!IMPORTANT]
-based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
+>
-upgrading from an older version of docker, the upgrade process may not
+> Docker 1.12 ships with an updated systemd unit file for rpm
-automatically install the updated version of the unit file, or fail to start
+based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
-the docker service if;
+> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
 
-- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+Starting the `docker service` will produce an error:
-- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
-
-Starting the docker service will produce an error:
 
     Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
 
@@ -755,16 +741,14 @@ systemctl restart docker` to reload changes and (re)start the docker daemon.
 ## 1.12.0 (2016-07-28)
 
 
-**IMPORTANT**: Docker 1.12.0 ships with an updated systemd unit file for rpm
+> [!IMPORTANT]
-based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When
+>
-upgrading from an older version of docker, the upgrade process may not
+> Docker 1.12.0 ships with an updated systemd unit file for rpm
-automatically install the updated version of the unit file, or fail to start
+based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). When upgrading from an older version of Docker, the upgrade process may not automatically install the updated version of the unit file, or fail to start the `docker service` if;
-the docker service if;
+> - the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+> - a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
 
-- the systemd unit file (`/usr/lib/systemd/system/docker.service`) contains local changes, or
+Starting the `docker service` will produce an error:
-- a systemd drop-in file is present, and contains `-H fd://` in the `ExecStart` directive
-
-Starting the docker service will produce an error:
 
     Failed to start docker.service: Unit docker.socket failed to load: No such file or directory.
 
@@ -782,9 +766,10 @@ To resolve this:
 After making those changes, run `sudo systemctl daemon-reload`, and `sudo
 systemctl restart docker` to reload changes and (re)start the docker daemon.
 
-**IMPORTANT**: With Docker 1.12, a Linux docker installation now has two
+> [!IMPORTANT]
-additional binaries; `dockerd`, and `docker-proxy`. If you have scripts for
+>
-installing docker, make sure to update them accordingly.
+> With Docker 1.12, a Linux `docker` installation now has two
+additional binaries; `dockerd`, and `docker-proxy`. If you have scripts for installing `docker`, make sure to update them accordingly.
 
 ### Builder
 
@@ -974,7 +959,9 @@ installing docker, make sure to update them accordingly.
 
 ## 1.11.0 (2016-04-13)
 
-**IMPORTANT**: With Docker 1.11, a Linux docker installation is now made of 4 binaries (`docker`, [`docker-containerd`](https://github.com/docker/containerd), [`docker-containerd-shim`](https://github.com/docker/containerd) and [`docker-runc`](https://github.com/opencontainers/runc)). If you have scripts relying on docker being a single static binaries, make sure to update them. Interaction with the daemon stay the same otherwise, the usage of the other binaries should be transparent. A Windows docker installation remains a single binary, `docker.exe`.
+> [!IMPORTANT]
+>
+> With Docker 1.11, a Linux Docker installation is now made of 4 binaries (`docker`, [`docker-containerd`](https://github.com/docker/containerd), [`docker-containerd-shim`](https://github.com/docker/containerd) and [`docker-runc`](https://github.com/opencontainers/runc)). If you have scripts relying on `docker` being a single static binaries, make sure to update them. Interaction with the daemon stay the same otherwise, the usage of the other binaries should be transparent. A Windows Docker installation remains a single binary, `docker.exe`.
 
 ### Builder
 
@@ -1223,9 +1210,11 @@ installing docker, make sure to update them accordingly.
 
 ## 1.10.0 (2016-02-04)
 
-**IMPORTANT**: Docker 1.10 uses a new content-addressable storage for images and layers.
+> [!IMPORTANT]
-A migration is performed the first time docker is run, and can take a significant amount of time depending on the number of images present.
+>
-Refer to this page on the wiki for more information: https://github.com/docker/docker/wiki/Engine-v1.10.0-content-addressability-migration
+> Docker 1.10 uses a new content-addressable storage for images and layers.
+
+A migration is performed the first time `docker` is run, and can take a significant amount of time depending on the number of images present. Refer to this page on the wiki for more information: https://github.com/docker/docker/wiki/Engine-v1.10.0-content-addressability-migration
 We also released a cool migration utility that enables you to perform the migration before updating to reduce downtime.
 Engine 1.10 migrator can be found on Docker Hub: https://hub.docker.com/r/docker/v1.10-migrator/
 

content/manuals/engine/storage/drivers/device-mapper-driver.md

@@ -835,13 +835,9 @@ storage driver.
   allowing you to share data among containers and persisting even when no
   running container is using them.
 
-- **Note**: when using `devicemapper` and the `json-file` log driver, the log
+  > [!NOTE]
-  files generated by a container are still stored in Docker's dataroot directory, 
+  >
-  by default `/var/lib/docker`.  If your containers generate lots of log messages, 
+  > When using `devicemapper` and the `json-file` log driver, the log files generated by a container are still stored in Docker's dataroot directory, by default `/var/lib/docker`.  If your containers generate lots of log messages, this may lead to increased disk usage or the inability to manage your system due to a full disk. You can configure a [log driver](/manuals/engine/logging/configure.md) to store your container logs externally.
-  this may lead to increased disk usage or the inability to manage your system due
-  to a full disk. You can configure a 
-  [log driver](/manuals/engine/logging/configure.md) to store your container
-  logs externally.
 
 ## Related Information
 

content/manuals/engine/storage/drivers/zfs-driver.md

@@ -20,10 +20,9 @@ The ZFS on Linux (ZoL) port is healthy and maturing. However, at this point in
 time it is not recommended to use the `zfs` Docker storage driver for production
 use unless you have substantial experience with ZFS on Linux.
 
-> ***Note***: There is also a FUSE implementation of ZFS on the Linux platform.
+> [!NOTE]
-> This is not recommended. The native ZFS driver (ZoL) is more tested, more
+>
-> performant, and is more widely used. The remainder  of this document refers
+> There is also a FUSE implementation of ZFS on the Linux platform. This is not recommended. The native ZFS driver (ZoL) is more tested, has better performance, and is more widely used. The remainder of this document refers to the native ZoL port.
-> to the native ZoL port.
 
 ## Prerequisites
 
@@ -38,8 +37,7 @@ use unless you have substantial experience with ZFS on Linux.
 
 > [!NOTE]
 >
-> There is no need to use `MountFlags=slave` because `dockerd` and `containerd`
+> There is no need to use `MountFlags=slave` because `dockerd` and `containerd` are in different mount namespaces.
-> are in different mount namespaces. 
 
 ## Configure Docker with the `zfs` storage driver
 

content/manuals/engine/swarm/how-swarm-mode-works/nodes.md

@@ -46,10 +46,9 @@ manager nodes.
 * An odd number `N` of manager nodes in the cluster tolerates the loss of at most `(N-1)/2` managers.
 Docker recommends a maximum of seven manager nodes for a swarm.
 
-    >**Important**
+    > [!IMPORTANT]
     >
-    > Adding more managers does NOT mean increased
+    > Adding more managers does NOT mean increased scalability or higher performance. In general, the opposite is true.
-    > scalability or higher performance. In general, the opposite is true.
 
 ## Worker nodes
 

content/manuals/engine/swarm/swarm-tutorial/_index.md

@@ -39,11 +39,9 @@ Amazon EC2 instances, or hosted in some other way. Check out
 One of these machines is a manager (called `manager1`) and two of them are
 workers (`worker1` and `worker2`).
 
->**Note**
+> [!NOTE]
 >
-> You can follow many of the tutorial steps to test single-node swarm
+> You can follow many of the tutorial steps to test single-node swarm as well, in which case you need only one host. Multi-node commands do not work, but you can initialize a swarm, create services, and scale them.
-> as well, in which case you need only one host. Multi-node commands do not
-> work, but you can initialize a swarm, create services, and scale them.
 
 #### Install Docker Engine on Linux machines
 

content/manuals/engine/swarm/swarm-tutorial/inspect-service.md

@@ -35,7 +35,7 @@ the Docker CLI to see details about the service running in the swarm.
     Endpoint Mode:  vip
     ```
 
-    >**Tip**
+    > [!TIP]
     >
     > To return the service details in json format, run the same command
     without the `--pretty` flag.
@@ -110,7 +110,7 @@ the Docker CLI to see details about the service running in the swarm.
 4.  Run `docker ps` on the node where the task is running to see details about
     the container for the task.
 
-    >**Tip**
+    > [!TIP]
     >
     > If `helloworld` is running on a node other than your manager node,
     you must ssh to that node.

content/manuals/extensions/settings-feedback.md

@@ -19,7 +19,7 @@ Docker Extensions is switched on by default. To change your settings:
 3. Next to **Enable Docker Extensions**, select or clear the checkbox to set your desired state.
 4. In the bottom-right corner, select **Apply & Restart**.
 
->**Note**
+> [!NOTE]
 >
 > If you are an [organization owner](/manuals/admin/organization/manage-a-team.md#organization-owner), you can turn off extensions for your users. Open the `settings-store.json` file, and set `"extensionsEnabled"` to `false`.
 > The `settings-store.json` file (or `settings.json` for Docker Desktop versions 4.34 and earlier) is located at:

content/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/limitations.md

@@ -16,7 +16,7 @@ Desktop was configured to use Windows Subsystem for Linux (aka WSL).
 Starting with Docker Desktop 4.20, ECI is supported when Docker Desktop is
 configured to use either Hyper-V or WSL 2.
 
->**Note**
+> [!NOTE]
 >
 > Docker Desktop requires WSL 2 version 1.1.3.0 or later. To get the current
 > version of WSL on your host, type `wsl --version`. If the command fails or if

content/reference/api/extensions-sdk/DockerDesktopClient.md

@@ -21,7 +21,7 @@ The `window.ddClient.backend` object can be used to communicate with the backend
 the extension metadata.
 The client is already connected to the backend.
 
->**Warning**
+> [!WARNING]
 >
 > It will be removed in a future version. Use [extension](DockerDesktopClient.md#extension) instead.
 
@@ -88,7 +88,7 @@ You can use the option `{"all": true}` to list all the running and stopped conta
 const containers = await window.ddClient.listContainers();
 ```
 
->**Warning**
+> [!WARNING]
 >
 > It will be removed in a future version. Use [listContainers](Docker.md#listcontainers) instead.
 
@@ -590,7 +590,7 @@ Opens an external URL with the system default browser.
 window.ddClient.openExternal("https://docker.com");
 ```
 
-**Warning**
+> [!WARNING]
 >
 > It will be removed in a future version. Use [openExternal](Host.md#openexternal) instead.
 
@@ -682,7 +682,7 @@ Display a toast message of type error.
 window.ddClient.toastError("message");
 ```
 
->**Warning**
+> [!WARNING]
 >
 > It will be removed in a future version. Use [error](Toast.md#error) instead.
 

layouts/shortcodes/admin-domain-audit.md

@@ -22,7 +22,7 @@ To audit your domains:
 
 You can invite all the uncaptured users to your organization using the exported CSV file. For more details, see [Invite members](/admin/organization/members/). Optionally, enforce single sign-on or enable SCIM to add users to your organization automatically. For more details, see {{ $sso_link }} or {{ $scim_link }}.
 
-> **Note**
+> [!NOTE]
 >
 > Domain audit may identify accounts of users who are no longer a part of your organization. If you don't want to add a user to your organization and you don't want the user to appear in future domain audits, you must deactivate the account or update the associated email address.
 >

layouts/shortcodes/admin-org-audit-log.html

@@ -12,7 +12,7 @@ To view the activity logs:
 1. Sign in to {{ $product_link }}.
 2. {{ $audit_navigation }}
 
-> **Note**
+> [!NOTE]
 >
 > Docker retains the activity data for a period of three months.
 
@@ -20,7 +20,7 @@ To view the activity logs:
 
 By default, all activities that occur are displayed on the **Activity** tab. Use the calendar option to select a date range and customize your results. After you have selected a date range, the activity logs of all the activities that occurred during that period are displayed.
 
-> **Note**
+> [!NOTE]
 >
 > Activities created by the Docker Support team as part of resolving customer issues appear in the activity logs as **dockersupport**.
 

layouts/shortcodes/admin-sso-management.md

@@ -17,6 +17,6 @@
 7. Select **Next** to confirm or change the default organization and team provisioning selections.
 8. Review the **Connection Summary** and select **Update connection**.
 
-> [!Note]
+> [!NOTE]
 >
 > If you want to re-add the domain, a new TXT record value is assigned. You must then complete the verification steps with the new TXT record value.