diff --git a/content/rancher/v2.5/en/logging/_index.md b/content/rancher/v2.5/en/logging/_index.md
index e6cb389914c..a5303c9f620 100644
--- a/content/rancher/v2.5/en/logging/_index.md
+++ b/content/rancher/v2.5/en/logging/_index.md
@@ -314,6 +314,13 @@ spec:
 In the above example, we ensure that our pod only runs on Linux nodes, and we add a `toleration` for the taint we have on all of our Linux nodes.
 You can do the same with Rancher's existing taints, or with your own custom ones.
 
+# 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.
+
 ### Windows Support
 
 Clusters with Windows workers support exporting logs from Linux nodes, but Windows node logs are currently unable to be exported.
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 a84570df8e4..6ea1e23b884 100644
--- a/content/rancher/v2.x/en/logging/v2.5/_index.md
+++ b/content/rancher/v2.x/en/logging/v2.5/_index.md
@@ -278,6 +278,8 @@ Let's break down what is happening here. First, we create a deployment of a cont
 
 # 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.