From d8d2b7ec97dbcb6e3253af831ce166999730d143 Mon Sep 17 00:00:00 2001
From: Tim Gross <tgross@hashicorp.com>
Date: Fri, 11 Sep 2020 10:38:30 -0400
Subject: [PATCH] docs: add chroot contents to Java driver docs (#8873)

---
 website/pages/docs/drivers/java.mdx | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/website/pages/docs/drivers/java.mdx b/website/pages/docs/drivers/java.mdx
index 4b686aa09..4782296d4 100644
--- a/website/pages/docs/drivers/java.mdx
+++ b/website/pages/docs/drivers/java.mdx
@@ -150,3 +150,29 @@ running as root, many of these mechanisms cannot be used.
 
 As a baseline, the Java jars will be run inside a Java Virtual Machine,
 providing a minimum amount of isolation.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).