Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   33470 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

LXC-CREATE(1)							 LXC-CREATE(1)

NAME
       lxc-create - creates a container

SYNOPSIS
       lxc-create  -n  name [ -f config_file ]	[ -t template ]	 [ -B backing‐
       store ]	[ -- template-options ]

DESCRIPTION
       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 /container 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 informa‐
       tion, 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.

OPTIONS
       -f config_file
	      Specify  the  configuration file to configure the virtualization
	      and isolation functionalities 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.  Alternatively, the full path to an  executable  tem‐
	      plate script can also be passed as a parameter.

       -B backingstore
	      'backingstore'  is  one  of  'dir',  'lvm',  'loop', 'btrfs', or
	      'best'. The default is 'dir', meaning that  the  container  root
	      filesystem   will	  be   a   directory   under   /container/con‐
	      tainer/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 subvol‐
	      ume. This allows snapshotted clones  to  be  created,  but  also
	      causes rsync --one-filesystem to treat it as a separate filesys‐
	      tem.  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 default,	lxc.   --thin‐
	      pool  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 cre‐
	      ate  a LV (and filesystem) of size SIZE rather than the default,
	      which is 1G.

	      If backingstore is 'best', then lxc will try, in	order,	btrfs,
	      zfs, lvm, and finally 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.

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

       -P, --lxcpath=PATH
	      Use an alternate container path. The default is /container.

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

SEE ALSO
       lxc(7), lxc-create(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
       Daniel Lezcano <daniel.lezcano@free.fr>

			  Thu Jul 3 13:01:56 PDT 2014		 LXC-CREATE(1)

Vote for polarhome