diff --git a/content/rancher/v2.5/en/logging/_index.md b/content/rancher/v2.5/en/logging/_index.md
index 541b5774e9d..6aa6c4be2c5 100644
--- a/content/rancher/v2.5/en/logging/_index.md
+++ b/content/rancher/v2.5/en/logging/_index.md
@@ -15,6 +15,7 @@ aliases:
 - [Uninstall Logging](#uninstall-logging)
 - [Role-based Access Control](#role-based-access-control)
 - [Configuring the Logging Application](#configuring-the-logging-application)
+- [Working with a Custom Docker Root Directory](#working-with-a-custom-docker-root-directory)
 - [Working with Taints and Tolerations](#working-with-taints-and-tolerations)
 
 # Changes in Rancher v2.5
@@ -282,6 +283,13 @@ Let's break down what is happening here. First, we create a deployment of a cont
 
 > **Note on syslog** Official `syslog` support is coming in Rancher v2.5.4. However, this example still provides an overview on using unsupported plugins.
 
+# Working with a Custom Docker Root Directory
+
+_Applies to v2.5.6+_
+
+If using a custom Docker root directory, you can set `global.dockerRootDirectory` in `values.yaml`.
+This will ensure that the Logging CRs created will use your specified path rather than the default Docker `data-root` location.
+
 # Working with Taints and Tolerations
 
 "Tainting" a Kubernetes node causes pods to repel running on that node.
diff --git a/content/rancher/v2.x/en/logging/v2.5/_index.md b/content/rancher/v2.x/en/logging/v2.5/_index.md
index 48d096cb223..851d3ba6c25 100644
--- a/content/rancher/v2.x/en/logging/v2.5/_index.md
+++ b/content/rancher/v2.x/en/logging/v2.5/_index.md
@@ -9,6 +9,7 @@ weight: 1
 - [Uninstall Logging](#uninstall-logging)
 - [Role-based Access Control](#role-based-access-control)
 - [Configuring the Logging Application](#configuring-the-logging-application)
+- [Working with a Custom Docker Root Directory](#working-with-a-custom-docker-root-directory)
 - [Working with Taints and Tolerations](#working-with-taints-and-tolerations)
 
 # Changes in Rancher v2.5