diff options
| author | Ian Lewis <ianlewis@google.com> | 2020-01-17 02:13:07 -0500 |
|---|---|---|
| committer | Ian Lewis <ianlewis@google.com> | 2020-01-17 02:13:07 -0500 |
| commit | 10ec43c775afaa49ca638cd2d411e975e06dbe78 (patch) | |
| tree | 70afacf314a23eacfc364be7d32171ecc05736b5 /content/docs/user_guide/FAQ.md | |
| parent | 712a2829e75c7c8fce6a24df774ec38f72d14348 (diff) | |
Clean up markdown lists
Diffstat (limited to 'content/docs/user_guide/FAQ.md')
| -rw-r--r-- | content/docs/user_guide/FAQ.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/content/docs/user_guide/FAQ.md b/content/docs/user_guide/FAQ.md index da742a41b..74acaa125 100644 --- a/content/docs/user_guide/FAQ.md +++ b/content/docs/user_guide/FAQ.md @@ -89,12 +89,12 @@ order to communicate to the DNS server. runsc network is isolated from the 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. -* Use [`--network=host`][host-net] option in runsc, however beware that it will - use the host network stack and is less secure. -* Use IPs instead of container names. -* Use [Kubernetes][k8s]. Container name lookup works fine in Kubernetes. +* Use default bridge network with `--link` to connect containers. Default + bridge doesn't use embedded DNS. +* Use [`--network=host`][host-net] option in runsc, however beware that it will + use the host network stack and is less secure. +* Use IPs instead of container names. +* Use [Kubernetes][k8s]. Container name lookup works fine in Kubernetes. [security-model]: /docs/architecture_guide/security/ [old-linux]: /docs/user_guide/networking/#gso |