summaryrefslogtreecommitdiffhomepage
path: root/content
diff options
context:
space:
mode:
authorAdin Scannell <ascannell@google.com>2019-07-10 10:38:53 -0700
committerIan Lewis <ianlewis@google.com>2019-07-11 07:34:35 +0900
commitd07850a808efb3415f2ff218675c9f73ac010fb4 (patch)
treecd4ac48efd054ba9eb0ede3c1dab6c58fa568758 /content
parentdf3fbd1ae63944c0e78d246584f138f8741a3e49 (diff)
Add fix for ptrace: unable to attach
Diffstat (limited to 'content')
-rw-r--r--content/docs/user_guide/FAQ.md11
1 files changed, 10 insertions, 1 deletions
diff --git a/content/docs/user_guide/FAQ.md b/content/docs/user_guide/FAQ.md
index a00ce48f4..22cda44bc 100644
--- a/content/docs/user_guide/FAQ.md
+++ b/content/docs/user_guide/FAQ.md
@@ -35,7 +35,7 @@ If you’re having problems running a container with `runsc` it’s most likely
to a compatibility issue or a missing feature in gVisor. See
[Debugging](../debugging/).
-### When I run my container, docker fails with `open /run/containerd/.../<containerid>/log.json: no such file or directory`.
+### When I run my container, docker fails with: `open /run/containerd/.../<containerid>/log.json: no such file or directory`
You are using an older version of Linux which doesn't support `memfd_create`.
gVisor requires Linux {{< required_linux >}} ([older Linux][old-linux]).
@@ -61,6 +61,15 @@ Note that `kubectl cp` works because it does the copy by exec'ing inside the
sandbox, and thus gVisor's internal cache is made aware of the new files and
directories.
+### I'm getting an error like: `panic: unable to attach: operation not permitted`
+
+Make sure that permissions and the owner is correct on the `runsc` binary.
+
+```bash
+sudo chown root:root /usr/local/bin/runsc
+sudo chmod 0755 /usr/local/bin/runsc
+```
+
### What's the security model?
See the [Security Model](../../architecture_guide/security/).