chore: fix some lint warnings in devicemapper docs

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson 2024-09-27 14:37:32 +02:00
parent 564705bb73
commit 6eae55dca8
1 changed files with 14 additions and 10 deletions

View File

@ -145,10 +145,11 @@ After you have satisfied the [prerequisites](#prerequisites), follow the steps
below to configure Docker to use the `devicemapper` storage driver in below to configure Docker to use the `devicemapper` storage driver in
`direct-lvm` mode. `direct-lvm` mode.
> [!WARNING]: Changing the storage driver makes any containers you have already > [!WARNING]
created inaccessible on the local system. Use `docker save` to save containers, > Changing the storage driver makes any containers you have already
and push existing images to Docker Hub or a private repository, so you do not > created inaccessible on the local system. Use `docker save` to save containers,
need to recreate them later. > and push existing images to Docker Hub or a private repository, so you do not
> need to recreate them later.
#### Allow Docker to configure direct-lvm mode #### Allow Docker to configure direct-lvm mode
@ -191,8 +192,9 @@ See all storage options for each storage driver in the
Restart Docker for the changes to take effect. Docker invokes the commands to Restart Docker for the changes to take effect. Docker invokes the commands to
configure the block device for you. configure the block device for you.
> [!WARNING]: Changing these values after Docker has prepared the block device > [!WARNING]
> for you is not supported and causes an error. > Changing these values after Docker has prepared the block device for you is
> not supported and causes an error.
You still need to [perform periodic maintenance tasks](#manage-devicemapper). You still need to [perform periodic maintenance tasks](#manage-devicemapper).
@ -227,8 +229,9 @@ assumes that the Docker daemon is in the `stopped` state.
4. Create a physical volume on your block device from step 1, using the 4. Create a physical volume on your block device from step 1, using the
`pvcreate` command. Substitute your device name for `/dev/xvdf`. `pvcreate` command. Substitute your device name for `/dev/xvdf`.
> [!WARNING]: The next few steps are destructive, so be sure that you have > [!WARNING]
> specified the correct device! > The next few steps are destructive, so be sure that you have specified
> the correct device.
```console ```console
$ sudo pvcreate /dev/xvdf $ sudo pvcreate /dev/xvdf
@ -651,7 +654,8 @@ $ sudo lvchange -ay docker/thinpool
## How the `devicemapper` storage driver works ## How the `devicemapper` storage driver works
> [!WARNING]: Do not directly manipulate any files or directories within > [!WARNING]
> Do not directly manipulate any files or directories within
> `/var/lib/docker/`. These files and directories are managed by Docker. > `/var/lib/docker/`. These files and directories are managed by Docker.
Use the `lsblk` command to see the devices and their pools, from the operating Use the `lsblk` command to see the devices and their pools, from the operating
@ -835,7 +839,7 @@ storage driver.
files generated by a container are still stored in Docker's dataroot directory, 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, 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 this may lead to increased disk usage or the inability to manage your system due
to a full disk. You can configure a to a full disk. You can configure a
[log driver](/manuals/engine/logging/configure.md) to store your container [log driver](/manuals/engine/logging/configure.md) to store your container
logs externally. logs externally.