docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ENGDOCS-2277 (#21255) 

<!--Delete sections as needed -->

## Description

Fix callouts

## Related issues or tickets

<!-- Related issues, pull requests, or Jira tickets -->

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
This commit is contained in:
Allie Sadler 2024-10-28 09:31:00 +00:00 committed by GitHub
parent 2fdfde2839
commit 01593f4b87
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/manuals/desktop/backup-and-restore.md
View File

@ -8,7 +8,7 @@ weight: 130
Use the following procedure to save and restore your images and container data. This is useful if you want to reset your VM disk or to move your Docker environment to a new Use the following procedure to save and restore your images and container data. This is useful if you want to reset your VM disk or to move your Docker environment to a new
computer, for example. computer, for example.
> Should I back up my containers? > [!IMPORTANT]
> >
> If you use volumes or bind-mounts to store your container data, backing up your containers may not be needed, but make sure to remember the options that were used when creating the container or use a [Docker Compose file](/reference/compose-file/_index.md) if you want to re-create your containers with the same configuration after re-installation. > If you use volumes or bind-mounts to store your container data, backing up your containers may not be needed, but make sure to remember the options that were used when creating the container or use a [Docker Compose file](/reference/compose-file/_index.md) if you want to re-create your containers with the same configuration after re-installation.

2
content/manuals/desktop/synchronized-file-sharing.md
View File

@ -47,7 +47,7 @@ File shares take a few seconds to initialize as files are copied into the Docker
When the status indicator displays **Watching for filesystem changes**, your files are available to the VM through all the standard bind mount mechanisms, whether that's `-v` in the command line or specified in your `compose.yml` file. When the status indicator displays **Watching for filesystem changes**, your files are available to the VM through all the standard bind mount mechanisms, whether that's `-v` in the command line or specified in your `compose.yml` file.
>**Note** > [!NOTE]
> >
> When you create a new service, setting the [bind mount option consistency](/reference/cli/docker/service/create.md#options-for-bind-mounts) to `:consistent` bypasses Synchronized file shares. > When you create a new service, setting the [bind mount option consistency](/reference/cli/docker/service/create.md#options-for-bind-mounts) to `:consistent` bypasses Synchronized file shares.

2
content/manuals/desktop/use-desktop/pause.md
View File

@ -11,7 +11,7 @@ You can manually pause Docker Desktop by selecting the Docker menu {{< inline-im
When you manually pause Docker Desktop, a paused status displays on the Docker menu and on the Docker Desktop Dashboard. You can still access the **Settings** and the **Troubleshoot** menu. When you manually pause Docker Desktop, a paused status displays on the Docker menu and on the Docker Desktop Dashboard. You can still access the **Settings** and the **Troubleshoot** menu.
>**Tip** > [!TIP]
> >
> The Resource Saver feature, available in Docker Desktop version 4.24 and later, is enabled by default and provides better > The Resource Saver feature, available in Docker Desktop version 4.24 and later, is enabled by default and provides better
> CPU and memory savings than the manual Pause feature. See [here](resource-saver.md) for more info. > CPU and memory savings than the manual Pause feature. See [here](resource-saver.md) for more info.

4
content/manuals/desktop/wsl/_index.md
View File

@ -26,7 +26,7 @@ Before you turn on the Docker Desktop WSL 2 feature, ensure you have:
- Met the Docker Desktop for Windows' [system requirements](https://docs.docker.com/desktop/install/windows-install/#system-requirements). - Met the Docker Desktop for Windows' [system requirements](https://docs.docker.com/desktop/install/windows-install/#system-requirements).
- Installed the WSL 2 feature on Windows. For detailed instructions, refer to the [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10). - Installed the WSL 2 feature on Windows. For detailed instructions, refer to the [Microsoft documentation](https://docs.microsoft.com/en-us/windows/wsl/install-win10).
>**Tip** > [!TIP]
> >
> For a better experience on WSL, consider enabling the WSL > For a better experience on WSL, consider enabling the WSL
> [autoMemoryReclaim](https://learn.microsoft.com/en-us/windows/wsl/wsl-config#experimental-settings) > [autoMemoryReclaim](https://learn.microsoft.com/en-us/windows/wsl/wsl-config#experimental-settings)
@ -51,7 +51,7 @@ Before you turn on the Docker Desktop WSL 2 feature, ensure you have:
Now `docker` commands work from Windows using the new WSL 2 engine. Now `docker` commands work from Windows using the new WSL 2 engine.
>**Tip** > [!TIP]
> >
> By default, Docker Desktop stores the data for the WSL 2 engine at `C:\Users\[USERNAME]\AppData\Local\Docker\wsl`. > By default, Docker Desktop stores the data for the WSL 2 engine at `C:\Users\[USERNAME]\AppData\Local\Docker\wsl`.
> If you want to change the location, for example, to another drive you can do so via the `Settings -> Resources -> Advanced` page from the Docker Dashboard. > If you want to change the location, for example, to another drive you can do so via the `Settings -> Resources -> Advanced` page from the Docker Dashboard.