]> @LXC_GENERATE_DATE@ lxc-execute 1 lxc-execute run an application inside a container. lxc-execute -n name -d -f config_file -s KEY=VAL -u, --uid uid -g, --gid gid -- command lxc-execute runs the specified command inside the container specified by name. 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 used. 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. (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. -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. -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. -u, --uid uid Executes the command with user ID uid inside the container. --g, --gid gid Executes the command with group ID gid inside the container. -- Signal the end of options and disables further option processing. Any arguments after the -- are treated as arguments to command. This option is useful when you want specify options to command and don't want lxc-execute to interpret them. &commonoptions; 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. &seealso; Daniel Lezcano daniel.lezcano@free.fr