From 3c250509d1b0cc133d2e7f2f2b769caa5a256eb8 Mon Sep 17 00:00:00 2001 From: nitkon Date: Wed, 24 Jul 2019 20:21:46 +0530 Subject: [PATCH] architecture.md: Fix networking info The networking part of the doc talks about the two ends of the veth pair. One end is in the container networking namespace and the other one should be in the host networking namespace. Fix this info. Fixes: #518 Signed-off-by: Nitesh Konkar niteshkonkar@in.ibm.com --- design/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/architecture.md b/design/architecture.md index 281215a929..68b58d27da 100644 --- a/design/architecture.md +++ b/design/architecture.md @@ -428,7 +428,7 @@ which is shared between containers In order to do so, container engines will usually add one end of a virtual ethernet (`veth`) pair into the container networking namespace. The other end of -the `veth` pair is added to the container network. +the `veth` pair is added to the host networking namespace. This is a very namespace-centric approach as many hypervisors (in particular QEMU) cannot handle `veth` interfaces. Typically, `TAP` interfaces are created for VM