From 86cb9c3ebbcd72f88708618fce01ce792262873e Mon Sep 17 00:00:00 2001 From: David Kwon Date: Thu, 21 Nov 2024 16:13:31 -0500 Subject: [PATCH] Update modules/administration-guide/pages/about-persistent-user-home.adoc Co-authored-by: Jana Vrbkova --- .../administration-guide/pages/about-persistent-user-home.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/administration-guide/pages/about-persistent-user-home.adoc b/modules/administration-guide/pages/about-persistent-user-home.adoc index 0c8e75c51f..97fa87b9be 100644 --- a/modules/administration-guide/pages/about-persistent-user-home.adoc +++ b/modules/administration-guide/pages/about-persistent-user-home.adoc @@ -41,7 +41,7 @@ Using the `stow` command to populate `/home/user` content in the persistent volu . Creating symbolic links is faster than creating copies of the `/home/user` folder content in the persistent volume. To put it differently, the persistent volume in this case contains symbolic links and not the actual files themselves. . If the tools image is updated with newer versions of existing binaries, configs, and files, the init container does not need to `stow` the new versions, as the existing symbolic links will link to the newer versions in `/home/tooling` already. -== Requirements for the tools image +.`persistUserHome` tools image requirements The `persistUserHome` depends on the tools image used for the workspace. By default {prod-short} uses the Universal Developer Image (UDI) for sample workspaces, which supports `persistUserHome` out of the box.