diff options
| author | Fabricio Voznika <fvoznika@google.com> | 2019-04-03 12:18:46 -0700 |
|---|---|---|
| committer | Fabricio Voznika <fvoznika@gmail.com> | 2019-04-08 11:34:06 -0700 |
| commit | 37433204a8ecda68ea2164315686006240bf11aa (patch) | |
| tree | 0e6f5dda405e0564a55b6eb60690b0e0d9bd3f45 /content/docs/user_guide/FAQ.md | |
| parent | c23efc31e2721ed192b19d082553cb99a391d24e (diff) | |
Edits to user guide + added filesystem section
Diffstat (limited to 'content/docs/user_guide/FAQ.md')
| -rw-r--r-- | content/docs/user_guide/FAQ.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/content/docs/user_guide/FAQ.md b/content/docs/user_guide/FAQ.md index 167933f9f..5e166ace3 100644 --- a/content/docs/user_guide/FAQ.md +++ b/content/docs/user_guide/FAQ.md @@ -20,12 +20,13 @@ not realize a new file was copied to a given directory. To invalidate the cache and force a refresh, create a file under the directory in question and list the contents again. +As a workaround, shared root filesystem can be enabled. See [Filesystem](../filesystem/). + This bug is tracked in [bug #4](https://github.com/google/gvisor/issues/4). Note that `kubectl cp` works because it does the copy by exec'ing inside the -sandbox, and thus gVisor cache is aware of the new files and dirs. - -There are also different filesystem modes that can be used to avoid this issue. +sandbox, and thus gVisor's internal cache is made aware of the new files and +directories. ### What's the security model? |