From 28bd7fe0210c8af4041918841d98cf8855945f79 Mon Sep 17 00:00:00 2001 From: jmwilkinson Date: Mon, 27 Sep 2021 16:36:04 -0700 Subject: [PATCH] Update filesystem.mdx (#11182) * Update filesystem.mdx Update summary of alloc directory to include information on access differences between task drivers and filesystem isolation modes. Co-authored-by: Tim Gross --- website/content/docs/internals/filesystem.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/website/content/docs/internals/filesystem.mdx b/website/content/docs/internals/filesystem.mdx index 62500fb87..8017f7382 100644 --- a/website/content/docs/internals/filesystem.mdx +++ b/website/content/docs/internals/filesystem.mdx @@ -42,8 +42,12 @@ allocation directory like the one below. log shipper. This is the directory that's provided to the task as the `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the "allocation working directory", which is the top-level directory. All tasks - in a task group can read and write to the `alloc/` directory. Within the - `alloc/` directory are three standard directories: + in a task group can read and write to the `alloc/` directory. But the full host + path may differ depending on the task driver's [filesystem isolation mode], so + tasks should always used the `NOMAD_ALLOC_DIR` environment variable + to find this path rather than relying on the specific implementation of the + [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation) + modes. Within the `alloc/` directory are three standard directories: - **alloc/data/**: This directory is the location used by the [`ephemeral_disk`] stanza for shared data.