summaryrefslogtreecommitdiffhomepage
path: root/docs/architecture_guide/why.md
diff options
context:
space:
mode:
authorAdin Scannell <ascannell@google.com>2019-04-09 10:19:17 -0700
committerShentubot <shentubot@google.com>2019-04-09 10:20:21 -0700
commitf18a8f958187aa52d028d1e3cc3dc0c03b742fed (patch)
tree5dbc8b7eabc3ea07f5eedd89b07c170a21b0cc4d /docs/architecture_guide/why.md
parentcf4ed408c355ffaaca92b574108815072572b872 (diff)
Update README.md to point to gvisor.dev
PiperOrigin-RevId: 242690968 Change-Id: I1ac2248b5ab3bcd95beed52ecddbb9f34eeb3775
Diffstat (limited to 'docs/architecture_guide/why.md')
-rw-r--r--docs/architecture_guide/why.md9
1 files changed, 0 insertions, 9 deletions
diff --git a/docs/architecture_guide/why.md b/docs/architecture_guide/why.md
deleted file mode 100644
index 2bf9c60fd..000000000
--- a/docs/architecture_guide/why.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Why gVisor?
-
-gVisor makes a different set of technical trade-offs compared to existing
-sandbox technologies, thus providing new tools and ideas for the container
-security landscape.
-
-As the developers of gVisor, we wanted an execution environment that was secure,
-simple, and lightweight and were able to make trade offs in other areas. We were
-not able to achieve that with existing solutions.