# LXC container driver

The libvirt LXC driver manages "Linux Containers". Containers are sets of processes with private namespaces which can (but don't always) look like separate machines, but do not have their own OS. Here are two example configurations. The first is a very light-weight "application container" which does not have it's own root image. You would start it using

### Example config version 1

    <domain type='lxc'>
    	<name>vm1</name>
    	<memory>500000</memory>
    	<os>
    		<type>exe</type>
    		<init>/bin/sh</init>
    	</os>
    	<vcpu>1</vcpu>
    	<clock offset='utc'/>
    	<on_poweroff>destroy</on_poweroff>
    	<on_reboot>restart</on_reboot>
    	<on_crash>destroy</on_crash>
    	<devices>
    		<emulator>/usr/libexec/libvirt_lxc</emulator>
    		<interface type='network'>
    			<source network='default'/>
    		</interface>
    		<console type='pty' />
    	</devices>
    </domain>

The next example assumes there is a private root filesystem (perhaps hand-crafted using busybox, or installed from media, debootstrap, whatever) under /opt/vm-1-root:

    <domain type='lxc'>
    	<name>vm1</name>
    	<memory>32768</memory>
    	<os>
    		<type>exe</type>
    		<init>/init</init>
    	</os>
    	<vcpu>1</vcpu>
    	<clock offset='utc'/>
    	<on_poweroff>destroy</on_poweroff>
    	<on_reboot>restart</on_reboot>
    	<on_crash>destroy</on_crash>
    	<devices>
    		<emulator>/usr/libexec/libvirt_lxc</emulator>
    		<filesystem type='mount'>
    			<source dir='/opt/vm-1-root'/>
    			<target dir='/'/>
    		</filesystem>
    		<interface type='network'>
    			<source network='default'/>
    		</interface>
    		<console type='pty' />
    	</devices>
    </domain>

In both cases, you can define and start a container using:

    virsh --connect lxc:/// define v1.xml
    virsh --connect lxc:/// start v1.xml

    virsh --connect lxc:/// console v1

Now doing 'ps -ef' will only show processes in the container, for instance.