:: RootR ::  Hosting Order Map Login   Secure Inter-Network Operations  
lxc-create(1) - phpMan

Command: man perldoc info search(apropos)  

lxc-create(1)                                                                       lxc-create(1)

       lxc-create - creates a container

       lxc-create {-n name} [-f config_file] {-t template} [-B backingstore] [-- template-

       lxc-create creates a system object where is stored the configuration information and where
       can be stored user information. The identifier name is used to specify the container to be
       used with the different lxc commands.

       The object is a directory created in /var/lib/lxc and identified by its name.

       The object is the definition of the different resources an application can use or can see.
       The  more  the configuration file contains information, the more the container is isolated
       and the more the application is jailed.

       If the configuration file config_file is not specified, the container will be created with
       the default isolation: processes, sysv ipc and mount points.

       -f config_file
              Specify  the configuration file to configure the virtualization and isolation func‐
              tionalities for the container.

       -t template
              'template' is the short name of an existing 'lxc-template' script that is called by
              lxc-create,  eg. busybox, debian, fedora, ubuntu or sshd.  Refer to the examples in
              /usr/share/lxc/templates for details of the expected  script  structure.   Alterna‐
              tively,  the full path to an executable template script can also be passed as a pa‐

       -B backingstore
              'backingstore' is one of 'dir', 'lvm', 'loop', 'btrfs', 'zfs', or 'best'.  The  de‐
              fault  is 'dir', meaning that the container root filesystem will be a directory un‐
              der /var/lib/lxc/container/rootfs.  This backing store  type  allows  the  optional
              --dir  ROOTFS  to  be specified, meaning that the container rootfs should be placed
              under the specified path, rather than the default. (The 'none' backingstore type is
              an  alias  for  'dir'.) If 'btrfs' is specified, then the target filesystem must be
              btrfs, and the container rootfs will be created as a  new  subvolume.  This  allows
              snapshotted  clones  to be created, but also causes rsync --one-filesystem to treat
              it as a separate filesystem.  If backingstore is 'lvm', then an  lvm  block  device
              will be used and the following further options are available: --lvname lvname1 will
              create an LV named lvname1 rather than the default, which is  the  container  name.
              --vgname  vgname1  will  create  the LV in volume group vgname1 rather than the de‐
              fault, lxc.  --thinpool thinpool1 will create the LV as a  thin-provisioned  volume
              in  the  pool  named  thinpool1 rather than the default, lxc.  --fstype FSTYPE will
              create an FSTYPE filesystem on the LV, rather than  the  default,  which  is  ext4.
              --fssize  SIZE  will  create a LV (and filesystem) of size SIZE rather than the de‐
              fault, which is 1G.

              If backingstore is 'best', then lxc will try, in order, btrfs, zfs, lvm, and final‐
              ly a directory backing store.

       -- template-options
              This  will  pass  template-options to the template as arguments. To see the list of
              options supported by the template, you can run lxc-create -t TEMPLATE -h.

       These options are common to most of lxc commands.

       -?, -h, --help
              Print a longer usage message than normal.

              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 ERROR. Possible values are :

              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

       The container already exists
              As  the  message mention it, you try to create a container but there is a container
              with the same name. You can use the lxc-ls command to list the available containers
              on the system.

       lxc(7), lxc-create(1), lxc-destroy(1), lxc-start(1), lxc-stop(1), lxc-execute(1), lxc-con‐
       sole(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)

       Daniel Lezcano <daniel.lezcano AT free.fr>

                                   Sat Apr 29 06:45:43 UTC 2017                     lxc-create(1)

rootr.net - man pages