From 12b1f28c09a21a6266ec6b761cf70b19dde6f9ac Mon Sep 17 00:00:00 2001 From: Sarah Sanders Date: Mon, 4 Nov 2024 08:45:05 -0800 Subject: [PATCH] Update content/manuals/engine/storage/drivers/device-mapper-driver.md Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com> --- content/manuals/engine/storage/drivers/device-mapper-driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/manuals/engine/storage/drivers/device-mapper-driver.md b/content/manuals/engine/storage/drivers/device-mapper-driver.md index a15bff1250..7eb9de9bb6 100644 --- a/content/manuals/engine/storage/drivers/device-mapper-driver.md +++ b/content/manuals/engine/storage/drivers/device-mapper-driver.md @@ -835,7 +835,7 @@ storage driver. allowing you to share data among containers and persisting even when no running container is using them. - > [!NOTE] vf + > [!NOTE] > > 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.