lxc-create man page on Slackware

Man page or keyword search:  
man Server   14563 pages
apropos Keyword Search (all sections)
Output format
Slackware logo
[printable version]

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

NAME
       lxc-create - creates a container

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

DESCRIPTION
       lxc-create creates a system object where is  stored  the	 configuration
       informations  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 informa‐
       tions, 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, fedo‐
	      ra,   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 'none', 'dir', 'lvm', or 'btrfs'. The
	      default is 'none', meaning that the  container  root  filesystem
	      will  be a directory under /var/lib/lxc/container/rootfs.	 'dir'
	      has the same meaning as 'none', but  also	 allows	 the  optional
	      --dir  ROOTFS to be specified, meaning that the container rootfs
	      should be placed under the specified path, rather than  the  de‐
	      fault.   The  option 'btrfs' need not be specified as it will be
	      used automatically if the /var/lib/lxc filesystem is found to be
	      btrfs.  If  backingstore is 'lvm', then an lvm block device will
	      be used and the following further options are  available:	 --lv‐
	      name lvname1 will create an LV named lvname1 rather than the de‐
	      fault, which is the container name. --vgname vgname1 will create
	      the  LV  in  volume  group vgname1 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.

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

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
	      -l command to list the available containers on the system.

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

AUTHOR
       Daniel Lezcano <daniel.lezcano@free.fr>

			  Tue Jul 9 14:17:14 CDT 2013		 lxc-create(1)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server Slackware

List of man pages available for Slackware

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net