Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
L
lxc
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
lxc
Commits
38005c54
Commit
38005c54
authored
Jan 13, 2015
by
Michael Adam
Committed by
Stéphane Graber
Jan 15, 2015
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: clarify the description of the veth network type in the manpage.
Signed-off-by:
Michael Adam
<
obnox@samba.org
>
Acked-by:
Stéphane Graber
<
stgraber@ubuntu.com
>
parent
db2930e1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
13 additions
and
13 deletions
+13
-13
lxc.container.conf.sgml.in
doc/lxc.container.conf.sgml.in
+13
-13
No files found.
doc/lxc.container.conf.sgml.in
View file @
38005c54
...
@@ -267,20 +267,20 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
...
@@ -267,20 +267,20 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
</para>
</para>
<para>
<para>
<option>veth:</option> a peer network device is created
<option>veth:</option> a virtual ethernet pair
with one side assigned to the container and the other
device is created with one side assigned to the container
side is attached to a bridge specified by
and the other side attached to a bridge specified by
the <option>lxc.network.link</option>. If the bridge is
the <option>lxc.network.link</option> option.
not specified, then the veth pair device will be created
If the bridge is not specified, then the veth pair device
but not attached to any bridge. Otherwise, the bridge
will be created but not attached to any bridge.
has to be setup before on the
Otherwise, the bridge has to be created on the system
system, <command>lxc</command> won't handle any
before starting the container.
configuration outside of the container. By
<command>lxc</command> won't handle any
default <command>lxc</command> choose a name for the
configuration outside of the container.
By default, <command>lxc</command> chooses a name for the
network device belonging to the outside of the
network device belonging to the outside of the
container, this name is handled
container, but if you wish to handle
by <command>lxc</command>, but if you wish to handle
this name yourselves, you can tell <command>lxc</command>
this name yourself, you can tell <command>lxc</command>
to set a specific name with
to set a specific name with
the <option>lxc.network.veth.pair</option> option (except for
the <option>lxc.network.veth.pair</option> option (except for
unprivileged containers where this option is ignored for security
unprivileged containers where this option is ignored for security
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment