|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|
|
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | COMMON OPTIONS | DIAGNOSTIC | SEE ALSO | COLOPHON |
|
|
|
lxc-start(1) lxc-start(1)
lxc-start - run an application inside a container.
lxc-start {-n name} [-f config_file] [-c console_device] [-L
console_logfile] [-d] [-F] [-p pid_file] [-s KEY=VAL]
[-C] [--share-[net|ipc|uts] name|pid] [command]
lxc-start runs the specified command inside the container speci‐
fied by name.
It will setup the container according to the configuration previ‐
ously defined with the lxc-create command or with the configura‐
tion file parameter. If no configuration is defined, the default
isolation is used.
If no command is specified, lxc-start will use the command de‐
fined in lxc.init.cmd or if not set, the default "/sbin/init"
command to run a system container.
-d, --daemon
Run the container as a daemon. As the container has no
more tty, if an error occurs nothing will be displayed,
the log file can be used to check the error. (This is the
default mode)
-F, --foreground
Run the container in the foreground. In this mode, the
container console will be attached to the current tty and
signals will be routed directly to the container.
-p, --pidfile pid_file
Create a file with the process id.
-f, --rcfile config_file
Specify the configuration file to configure the virtual‐
ization and isolation functionalities for the container.
This configuration file if present will be used even if
there is already a configuration file present in the pre‐
viously created container (via lxc-create).
-c, --console console_device
Specify a device to use for the container's console, for
example /dev/tty8. If this option is not specified the
current terminal will be used unless -d is specified.
-L, --console-log console_logfile
Specify a file to log the container's console output to.
-s, --define KEY=VAL
Assign value VAL to configuration variable KEY. This over‐
rides any assignment done in config_file.
-C, --close-all-fds
If any file descriptors are inherited, close them. If this
option is not specified, then lxc-start will exit with
failure instead. Note: --daemon implies --close-all-fds.
--share-net name|pid
Inherit a network namespace from a name container or a
pid. The network namespace will continue to be managed by
the original owner. The network configuration of the
starting container is ignored and the up/down scripts
won't be executed.
--share-ipc name|pid
Inherit an IPC namespace from a name container or a pid.
--share-uts name|pid
Inherit a UTS namespace from a name container or a pid.
The starting LXC will not set the hostname, but the con‐
tainer OS may do it anyway.
These options are common to most of lxc commands.
-?, -h, --help
Print a longer usage message than normal.
--usage
Give the usage message
-q, --quiet
mute on
-P, --lxcpath=PATH
Use an alternate container path. The default is
/var/lib/lxc.
-o, --logfile=FILE
Output to an alternate log FILE. The default is no log.
-l, --logpriority=LEVEL
Set log priority to LEVEL. The default log priority is ER‐
ROR. Possible values are : FATAL, ALERT, CRIT, WARN, ER‐
ROR, NOTICE, INFO, DEBUG, TRACE.
Note that this option is setting the priority of the
events log in the alternate log file. It do not have ef‐
fect on the ERROR events log on stderr.
-n, --name=NAME
Use container identifier NAME. The container identifier
format is an alphanumeric string.
--rcfile=FILE
Specify the configuration file to configure the virtual‐
ization and isolation functionalities for the container.
This configuration file if present will be used even if
there is already a configuration file present in the pre‐
viously created container (via lxc-create).
--version
Show the version number.
The container is busy
The specified container is already running an application.
You should stop it before reuse this container or create a
new one.
lxc(7), lxc-create(1), lxc-copy(1), lxc-destroy(1), lxc-start(1),
lxc-stop(1), lxc-execute(1), lxc-console(1), lxc-monitor(1),
lxc-wait(1), lxc-cgroup(1), lxc-ls(1), lxc-info(1),
lxc-freeze(1), lxc-unfreeze(1), lxc-attach(1), lxc.conf(5)
This page is part of the lxc (Linux containers) project. Infor‐
mation about the project can be found at
⟨http://linuxcontainers.org/⟩. If you have a bug report for this
manual page, send it to [email protected].
This page was obtained from the project's upstream Git repository
⟨https://github.com/lxc/lxc.git⟩ on 2024-06-14. (At that time,
the date of the most recent commit that was found in the
repository was 2024-06-05.) If you discover any rendering
problems in this HTML version of the page, or you believe there
is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
[email protected]
2024-04-03 lxc-start(1)
Pages that refer to this page: lxc-attach(1), lxc-autostart(1), lxc-cgroup(1), lxc-checkconfig(1), lxc-checkpoint(1), lxc-config(1), lxc-console(1), lxc-copy(1), lxc-create(1), lxc-destroy(1), lxc-device(1), lxc-execute(1), lxc-freeze(1), lxc-info(1), lxc-ls(1), lxc-monitor(1), lxc-snapshot(1), lxc-start(1), lxc-stop(1), lxc-top(1), lxc-unfreeze(1), lxc-unshare(1), lxc-update-config(1), lxc-user-nic(1), lxc-usernsexec(1), lxc-wait(1), lxc.container.conf(5), lxc.system.conf(5), lxc(7)
|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|