Linux Certif

Toute la documentation sur la certification Linux LPI

lxc-start

NAME

lxc-start - run an application inside a container.

SYNOPSIS

lxc-start -n name [-f config_file] [-s KEY=VAL] [command]

DESCRIPTION

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

The orphan process group and daemon are not supported by this command, use the lxc-execute command instead.

If no command is specified, lxc-start will use the default "/sbin/init" command to run a system container.

OPTIONS

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

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

COMMON OPTIONS

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

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

DIAGNOSTIC

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

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-unfreeze(1), lxc.conf(5)

AUTHOR

Daniel Lezcano <daniel.lezcano@free.fr>