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
d9e80daf
Commit
d9e80daf
authored
May 15, 2013
by
Dwight Engen
Committed by
Serge Hallyn
May 16, 2013
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/lxc.conf minor clarifications
Signed-off-by:
Dwight Engen
<
dwight.engen@oracle.com
>
Signed-off-by:
Serge Hallyn
<
serge.hallyn@ubuntu.com
>
parent
627fe3b4
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
16 deletions
+23
-16
lxc.conf.sgml.in
doc/lxc.conf.sgml.in
+23
-16
No files found.
doc/lxc.conf.sgml.in
View file @
d9e80daf
...
@@ -65,8 +65,8 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
...
@@ -65,8 +65,8 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<para>
<para>
The configuration file defines the different system resources to
The configuration file defines the different system resources to
be assigned for the container. At present, the utsname, the
be assigned for the container. At present, the utsname, the
network, the mount points, the root file system
and the control
network, the mount points, the root file system
, the user namespace,
groups are supported.
and the control
groups are supported.
</para>
</para>
<para>
<para>
...
@@ -80,7 +80,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
...
@@ -80,7 +80,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<para>
<para>
Allows to set the architecture for the container. For example,
Allows to set the architecture for the container. For example,
set a 32bits architecture for a container running 32bits
set a 32bits architecture for a container running 32bits
binaries on a 64bits host. Th
at fix
the container scripts
binaries on a 64bits host. Th
is fixes
the container scripts
which rely on the architecture to do some work like
which rely on the architecture to do some work like
downloading the packages.
downloading the packages.
</para>
</para>
...
@@ -258,7 +258,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
...
@@ -258,7 +258,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
specify an action to do for the
specify an action to do for the
network.
network.
</para>
</para>
<para><option>up:</option> activates the interface.
<para><option>up:</option> activates the interface.
</para>
</para>
</listitem>
</listitem>
...
@@ -448,7 +448,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
...
@@ -448,7 +448,7 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<para>
<para>
If the container is configured with a root filesystem and the
If the container is configured with a root filesystem and the
inittab file is setup to use the console, you may want to specify
inittab file is setup to use the console, you may want to specify
where
goes the output of this console
.
where
the output of this console goes
.
</para>
</para>
<variablelist>
<variablelist>
<varlistentry>
<varlistentry>
...
@@ -471,14 +471,14 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
...
@@ -471,14 +471,14 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<refsect2>
<refsect2>
<title>Console through the ttys</title>
<title>Console through the ttys</title>
<para>
<para>
If the container is configured with a root filesystem and the
This option is useful if the container is configured with a root
inittab file is setup to launch a getty on the ttys. This
filesystem and the inittab file is setup to launch a getty on the
option will specify the number of ttys to be available for the
ttys. The option specifies the number of ttys to be available for
container. The number of getty
in the inittab file of the
the container. The number of gettys
in the inittab file of the
container should not be greater than the number of ttys
container should not be greater than the number of ttys
specified
specified in this configuration file, otherwise the excess
in this option, otherwise the excess getty sessions will die and
getty sessions will die and respawn indefinitly giving
respawn indefinitely giving annoying messages on the console or in
annoying messages on the console
.
<filename>/var/log/messages</filename>
.
</para>
</para>
<variablelist>
<variablelist>
<varlistentry>
<varlistentry>
...
@@ -590,13 +590,20 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
...
@@ -590,13 +590,20 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
<para>
<para>
specify a file location in
specify a file location in
the <filename>fstab</filename> format, containing the
the <filename>fstab</filename> format, containing the
mount information
s
. If the rootfs is an image file or a
mount information. If the rootfs is an image file or a
device block
and the fstab is used to mount a point
block device
and the fstab is used to mount a point
somewhere in this rootfs, the path of the rootfs mount
somewhere in this rootfs, the path of the rootfs mount
point should be prefixed with the
point should be prefixed with the
<filename>@LXCROOTFSMOUNT@</filename> default path or
<filename>@LXCROOTFSMOUNT@</filename> default path or
the value of <option>lxc.rootfs.mount</option> if
the value of <option>lxc.rootfs.mount</option> if
specified.
specified. Note that when mounting a filesystem from an
image file or block device the third field (fs_vfstype)
cannot be auto as with
<citerefentry>
<refentrytitle>mount</refentrytitle>
<manvolnum>8</manvolnum>
</citerefentry>
but must be explicitly specified.
</para>
</para>
</listitem>
</listitem>
</varlistentry>
</varlistentry>
...
...
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