lxc-execute - run an application inside a container.
lxc-execute -n name [-f config_file] [-s KEY=VAL ] command
lxc-execute runs the specified command inside the container specified
It will setup the container according to the configuration previously
defined with the lxc-create command or with the configuration file
parameter. If no configuration is defined, the default isolation is
This command is mainly used when you want to quickly launch an
application in an isolated environment.
lxc-execute command will run the specified command into the container
via an intermediate process, lxc-init. This lxc-init after launching
the specified command, will wait for its end and all other reparented
processes. (that allows to support daemons in the container). In
other words, in the container, lxc-init has the pid 1 and the first
process of the application has the pid 2.
The above lxc-init is designed to forward received signals to the
started command. So lxc-kill (1) sent signal is received by the user
specified command (pid 2 in the container).
-f, --rcfile config_file
Specify the configuration file to configure the virtualization
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 previously created
container (via lxc-create).
-s, --define KEY=VAL
Assign value VAL to configuration variable KEY. This overrides
any assignment done in config_file.
These options are common to most of lxc commands.
-?, -h, --help
Print a longer usage message than normal.
Give the usage message
Output to an alternate log FILE. The default is no log.
Set log priority to LEVEL. The default log priority is ERROR.
Possible values are : FATAL, CRIT, WARN, ERROR, NOTICE, INFO,
Note that this option is setting the priority of the events log
in the alternate log file. It do not have effect on the ERROR
events log on stderr.
Use container identifier NAME. The container identifier format
is an alphanumeric string.
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(1), lxc-create(1), lxc-destroy(1), lxc-start(1), lxc-stop(1), lxc-
execute(1), lxc-kill(1), lxc-console(1), lxc-monitor(1), lxc-wait(1),
lxc-cgroup(1), lxc-ls(1), lxc-ps(1), lxc-info(1), lxc-freeze(1), lxc-
Daniel Lezcano <firstname.lastname@example.org>
26 July 2010