From 9b9e5d63e03ef99150eef79c0284b2e40c03d005 Mon Sep 17 00:00:00 2001 From: Ayoub Bousselmi Date: Fri, 11 Jan 2019 11:31:05 +0100 Subject: [PATCH] Docs: network connect is no longer a limitation Remove the `network connect` limitation from `Limitations.md` as the limitation has been removed. Fixes #287. Signed-off-by: Ayoub Bousselmi --- Limitations.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/Limitations.md b/Limitations.md index bb349894d9..6febccc7af 100644 --- a/Limitations.md +++ b/Limitations.md @@ -116,16 +116,6 @@ All other configurations are supported and are working properly. ## Networking -### Adding networks dynamically - -The runtime does not currently support adding networks to an already -running container (`docker network connect`). - -The VM network configuration is set up with what is defined by the CNM -plugin at startup time. Although it is possible to watch the networking namespace on the host to discover and propagate new networks at runtime, it is currently not implemented. - -See https://github.com/kata-containers/runtime/issues/113 for more information. - ### Docker swarm support The newest version of Docker supported is specified by the