summaryrefslogtreecommitdiffhomepage
path: root/content
diff options
context:
space:
mode:
authorIan Lewis <ianlewis@google.com>2020-04-02 19:26:22 -0400
committerIan Lewis <ianlewis@google.com>2020-04-03 09:54:21 +0900
commitc6be49273b7fccc6ee53ede4ca87af4dac1c2474 (patch)
tree48ebfa09de803a2e324373c2a03cf253252cfc89 /content
parent4421f4ad9a5b97cbfa064bbbe8cb8a49ab915f5f (diff)
Add header for final paragraph
Diffstat (limited to 'content')
-rw-r--r--content/blog/2_networking_security/index.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/content/blog/2_networking_security/index.md b/content/blog/2_networking_security/index.md
index 29b010820..f209e62ff 100644
--- a/content/blog/2_networking_security/index.md
+++ b/content/blog/2_networking_security/index.md
@@ -59,4 +59,6 @@ The goal of the Secure by Default principle is to make it easy to securely sandb
Another way in which gVisor makes it easy to securely sandbox containers is by allowing applications to run unmodified, with no special configuration needed. In order to do this, gVisor needs to support all of the features and syscalls that applications use. Neither seccomp nor gVisor's passthrough mode can do this as applications commonly use syscalls which are too dangerous to be included in a secure policy. Even if this dream isn't fully realized today, gVisor's architecture with Netstack makes this possible.
+## Give Netstack a Try
+
If you haven't already, try running a workload in gVisor with Netstack. You can find instructions on how to get started in our [Quick Start](https://gvisor.dev/docs/user_guide/quick_start/docker/). We want to hear about both your successes and any issues you encounter. We welcome your contributions, whether that be verbal feedback or code contributions, via our [Gitter channel](https://gitter.im/gvisor/community), [email list](https://groups.google.com/forum/#!forum/gvisor-users), [issue tracker](https://gvisor.dev/issue/new), and [Github repository](https://github.com/google/gvisor). Feel free to express interest in an [open issue](https://gvisor.dev/issue/), or reach out if you aren't sure where to start.