From 38005c5436d8a929141b7e8c0314dc5fd1c403f1 Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Tue, 13 Jan 2015 22:27:08 +0100 Subject: [PATCH] doc: clarify the description of the veth network type in the manpage. MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Michael Adam Acked-by: Stéphane Graber --- doc/lxc.container.conf.sgml.in | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/doc/lxc.container.conf.sgml.in b/doc/lxc.container.conf.sgml.in index 6d4daac07..8652373cc 100644 --- a/doc/lxc.container.conf.sgml.in +++ b/doc/lxc.container.conf.sgml.in @@ -267,20 +267,20 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA - a peer network device is created - with one side assigned to the container and the other - side is attached to a bridge specified by - the . If the bridge is - not specified, then the veth pair device will be created - but not attached to any bridge. Otherwise, the bridge - has to be setup before on the - system, lxc won't handle any - configuration outside of the container. By - default lxc choose a name for the + a virtual ethernet pair + device is created with one side assigned to the container + and the other side attached to a bridge specified by + the option. + If the bridge is not specified, then the veth pair device + will be created but not attached to any bridge. + Otherwise, the bridge has to be created on the system + before starting the container. + lxc won't handle any + configuration outside of the container. + By default, lxc chooses a name for the network device belonging to the outside of the - container, this name is handled - by lxc, but if you wish to handle - this name yourself, you can tell lxc + container, but if you wish to handle + this name yourselves, you can tell lxc to set a specific name with the option (except for unprivileged containers where this option is ignored for security -- 2.47.2