There is currently no GUI to create a root file system. You will thus need to open a terminal and use zypper as user root to populate the new root file system. In the following steps, the new root file system will be created in /PATH/TO/ROOTFS.

1. Add the openSUSE Leap repository and the corresponding update repository to the new root file system:

   root # zypper --root /PATH/TO/ROOTFS ar http://download.opensuse.org/distribution/leap/42.3/repo/oss/ OSS
   root # zypper --root /PATH/TO/ROOTFS ar http://download.opensuse.org/update/leap/42.3/oss/ Update-OSS

2. Refresh the repositories:

   root # zypper --root /PATH/TO/ROOTFS ref

3. Install a minimal system:

   root # zypper --root /PATH/TO/ROOTFS in -t pattern minimal_base

4. Set the root password:

   root # echo "ttyS0" >>/PATH/TO/ROOTFS/etc/securetty
   root # echo "root:YOURPASSWD" | chpasswd -R /PATH/TO/ROOTFS

1. Start Virtual Machine Manager.

2. (Optional) If not already present, add a local LXC connection by clicking File › Add Connection.

   Select LXC (Linux Containers) as the hypervisor and click Connect.

3. Select the localhost (LXC) connection and click File New Virtual Machine menu.

4. Activate Operating system container and click Forward.

5. Type the path to the root file system from Procedure 30.1, “Creating a Root File System” and click the Forward button.

6. Choose the maximum amount of memory and CPUs to allocate to the container. Then click the Forward button.

7. Type in a name for the container. This name will be used for all virsh commands on the container.

   Click Advanced options. Select the network to connect the container to and click the Finish button: the container will then be created and started. A console will also be automatically opened.

Network devices and hostdev devices with network capabilities can be provided with one or more IP addresses to set on the network device in the guest. However, some hypervisors or network device types will simply ignore them or only use the first one.

1. Edit the container XML configuration using virsh:

   tux > virsh -c lxc:/// edit MYCONTAINER

2. The following example shows how to set one or multiple IP addresses:

   [...]
   <devices>
    <interface type='network'>
     <source network='default'/>
     <target dev='vnet0'/>
     <ip address='192.168.122.5' prefix='24'/>
     <ip address='192.168.122.5' prefix='24' peer1='10.0.0.10'/>
      <route family2='ipv4' address3='192.168.122.0' prefix4='24'
             gateway5='192.168.122.1'/>
      <route family2='ipv4' address3='192.168.122.8' gateway5='192.168.122.1'/>
    </interface>
    [...]
    <hostdev mode='capabilities' type='net'>
     <source>
      <interface>eth0</interface>
     </source>
     <ip address='192.168.122.6' prefix='24'/>
     <route family='ipv4' address='192.168.122.0' prefix='24' gateway='192.168.122.1'/>
     <route family='ipv4' address='192.168.122.8' gateway='192.168.122.1'/>
    </hostdev>
   </devices>
   [...]

   1	Optional attribute. Holds the IP address of the other end of a point-to-point network device.
   2	Can be set to either ipv4 or ipv6.
   3	Contains the IP address.
   4	Optional parameter (will be automatically set if not specified). Defines the number of 1 bits in the netmask. For IPv4, the default prefix is determined according to the network “class” (A, B, or C). For IPv6, the default prefix is 64.
   5	If you do not specify a default gateway in the XML file, none will be set.

3. You can also add route elements to define IP routes to add in the guest. These are used by the LXC driver.

   [...]
   <devices>
    <interface type1='ethernet'>
     <source>2
      <ip address3='192.168.123.1' prefix='24'/>
      <ip address4='10.0.0.10' prefix='24' peer='192.168.122.5'/>
      <route5 family='ipv4' address='192.168.42.0' prefix='24'
               gateway='192.168.123.4'/>
     </source>
     [...]
    </interface>
    [...]
   </devices>
   [...]

   1	Network devices of type ethernet can optionally be provided with one or multiple IP addresses (3, 4) and with one or multiple routes (5) to set on the host side of the network device. These are configured as subelements of the source element (2) of the interface. They have the same attributes as the similarly named elements used to configure the guest side of the interface (see the step above).
   3	First IP address for the network device of type ethernet.
   4	Second IP address for the network device of type ethernet.
   5	Route to set on the host side of the network device.

   Find further details about the attributes of this element at http://libvirt.org/formatnetwork.html#elementsStaticroute.

4. Save the changes and exit the editor.

1. Start Virtual Machine Manager.

2. (Optional) If not already present, add a local LXC connection by clicking File › Add Connection.

   Select LXC (Linux Containers) as the hypervisor and click Connect.

3. Select the localhost (LXC) connection and click File New Virtual Machine menu.

4. Activate Application container and click Forward.

   Set the path to the application to be launched. As an example, the field is filled with /bin/sh, which is fine to create a first container. Click Forward.

5. Choose the maximum amount of memory and CPUs to allocate to the container. Click Forward.

6. Type in a name for the container. This name will be used for all virsh commands on the container.

   Click Advanced options. Select the network to connect the container to and click Finish. The container will be created and started. A console will be opened automatically.

   Note that the container will be destroyed after the application has finished running.

1. Edit the container XML configuration using virsh:

   tux > virsh -c lxc:/// edit MYCONTAINER

2. Add the following to the XML configuration, save it and exit the editor.

   <domain>
       ...
       <seclabel type="dynamic" model="apparmor"/>
       ...
   </domain>

3. With this configuration, an AppArmor profile for the container will be created in the /etc/apparmor.d/libvirt directory. The default profile only allows the minimum applications to run in the container. This can be changed by modifying the libvirt-CONTAINER-uuid file: this file is not overwritten by libvirt.