diff options
| author | Fabricio Voznika <fvoznika@google.com> | 2019-09-09 17:06:36 -0700 |
|---|---|---|
| committer | Ian Lewis <ianlewis@google.com> | 2019-09-10 13:43:32 +0900 |
| commit | 741c9bb99a48d597dd714543c2c7008d4005cc11 (patch) | |
| tree | 151fff45a1cf4a011f018ebd34d4568b2dd4b611 | |
| parent | cac17854648c71d00e8067314fd144525964dd53 (diff) | |
mend
| -rw-r--r-- | content/docs/user_guide/FAQ.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/content/docs/user_guide/FAQ.md b/content/docs/user_guide/FAQ.md index c266446dc..19358e8db 100644 --- a/content/docs/user_guide/FAQ.md +++ b/content/docs/user_guide/FAQ.md @@ -27,7 +27,7 @@ Binaries run in gVisor should be built for the Yes. Please see the [Docker Quick Start](/docs/user_guide/docker/). -### Can I run Kubernets pods using gVisor. +### Can I run Kubernetes pods using gVisor. Yes. Please see the [Docker Quick Start](/docs/user_guide/kubernetes/). @@ -80,12 +80,14 @@ sudo chmod 0755 /usr/local/bin/runsc ### My container cannot resolve another container's name when using Docker user defined bridge +This is normally indicated by errors like `bad address 'container-name'` when +trying to communicate to another container in the same network. + Docker user defined bridge uses an embedded DNS server bound to the loopback interface on address 127.0.0.10. This requires access to the host network in order to communicate to the DNS server. runsc network is isolated from the -host, therefore it cannot access the DNS server on the host network without -breaking the sandbox isolation. There are a few different workarounds you can -try: +host and cannot access the DNS server on the host network without breaking the +sandbox isolation. There are a few different workarounds you can try: * Use default bridge network with `--link` to connect containers. Default bridge doesn't use embedded DNS. |