summaryrefslogtreecommitdiffhomepage
path: root/content/docs/user_guide
diff options
context:
space:
mode:
Diffstat (limited to 'content/docs/user_guide')
-rw-r--r--content/docs/user_guide/FAQ.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/content/docs/user_guide/FAQ.md b/content/docs/user_guide/FAQ.md
index b94b93b1f..b0d0cd4a2 100644
--- a/content/docs/user_guide/FAQ.md
+++ b/content/docs/user_guide/FAQ.md
@@ -2,17 +2,18 @@
title = "FAQ"
weight = 1000
+++
-## My container runs fine with `runc` but fails with `runsc`
+
+### My container runs fine with `runc` but fails with `runsc`
If you’re having problems running a container with `runsc` it’s most likely due
to a compatibility issue or a missing feature in gVisor. See
[Debugging](../debugging/).
-## When I run my container, docker fails with: `flag provided but not defined: -console`
+### When I run my container, docker fails with: `flag provided but not defined: -console`
You're using an old version of Docker. See [Docker Quick Start](../docker/).
-## I can’t see a file copied with: `docker cp`
+### I can’t see a file copied with: `docker cp`
For performance reasons, gVisor caches directory contents, and therefore it may
not realize a new file was copied to a given directory. To invalidate the cache
@@ -27,10 +28,10 @@ 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.
See [Filesystem](../filesystem/).
-## What's the security model?
+### What's the security model?
See the [Security Model](../../architecture_guide/security/).
-## What's the expected performance?
+### What's the expected performance?
See the [Performance Guide](../../architecture_guide/performance/).