lxc-execute(1) — Linux manual page

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | COMMON OPTIONS | DIAGNOSTIC | SEE ALSO | AUTHOR | COLOPHON

LXC-EXECUTE(1)                                            LXC-EXECUTE(1)

NAME         top

       lxc-execute - run an application inside a container.

SYNOPSIS         top

       lxc-execute -n name [ -d ]  [ -f config_file ]  [ -s KEY=VAL ]  [
       -u, --uid uid ]  [ -g, --gid gid ]  [ -- command ]

DESCRIPTION         top

       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.

OPTIONS         top

       -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.

COMMON OPTIONS         top

       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
              /usr/local/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
              ERROR. Possible values are : FATAL, CRIT, WARN, ERROR,
              NOTICE, INFO, DEBUG.

              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.

       -n, --name=NAME
              Use container identifier NAME.  The container identifier
              format is an alphanumeric string.

       --rcfile=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).

       --version
              Show the version number.

DIAGNOSTIC         top

       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.

SEE ALSO         top

       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)

AUTHOR         top

       Daniel Lezcano <daniel.lezcano@free.fr>

COLOPHON         top

       This page is part of the lxc (Linux containers) project.
       Information about the project can be found at 
       ⟨http://linuxcontainers.org/⟩.  If you have a bug report for this
       manual page, send it to lxc-devel@lists.linuxcontainers.org.
       This page was obtained from the project's upstream Git repository
       ⟨git://github.com/lxc/lxc⟩ on 2021-04-01.  (At that time, the
       date of the most recent commit that was found in the repository
       was 2021-04-01.)  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
       man-pages@man7.org

                               2021-04-01                 LXC-EXECUTE(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-usernsexec(1)lxc-wait(1)lxc.container.conf(5)lxc.system.conf(5)lxc(7)