You have to have a <code>debootstrap </code> working for Gutsy, i.e. you should have* <code>debootstrap </code> and its dependencies* <code>/usr/lib/debootstrap/scripts/gutsy </code> file

The simplest way to have it all is to work on an Ubunty Ubuntu Gutsy system (be it on a real machine or inside a VEcontainer). If you don't have <code>debootstrap </code> installed, this is the command to install it:

You need vzctl-3.0.19 22 or later to work with Ubuntu Gutsy Gibbon. If vzctl-3.0.18 or earlier is used, you will not be able to run your VEUbuntu Gutsy container. See {{bug|662}} for details. Note: Older versions of vzctl are working if you install <code>sysvinit</code> (which will remove <code>upstart</code>). The only problem I had was the network did not start, so I added "/etc/init.d/networking restart" to /etc/re.local.

Create some a working directory:

[HW]# mkdir gutsy-chroot

[HW]# debootstrap [--arch ''ARCH'' ] gutsy gutsy-chroot

Substitute your architecture instead If ARCH of CT0 is equal to container, you can skip the --arch option, but if you need to build an OS template for another ''ARCH''. For example, specify it explicitly:* for AMD64/x86_64, use <code>amd64</code> or * for ia64IA64, use <code>ia64</code>. For * for i386 <code>i386 you do not have to give this option.</code>

=== Preparing/starting a VE container ===

Now then you have an installation created by <code>debootstrap</code>, you can run it as a VEcontainer. In the example below VE CT ID of 777 is used; of course you can use any other non-allocated ID.

You should move the contents of gutsy-chroot directory into new VE ==== Moving installation to container private area, like this:====

# mkdir /vz/private/777 # mv You should move the contents of gutsy-chroot/ /vz/directory into new container private/777area, like this:

# mv gutsy-chroot /vz/private/777 ==== Setting VE container config ====An initial config for the [[VEcontainer]] is needed:

==== Setting VE container OSTEMPLATE ====Also, we need <ttcode>OSTEMPLATE</ttcode> to be set in VE container configuration file, for the [[vzctl]] to work properly.

==== Setting VE container IP address ====For the [[VEcontainer]] to be able to download updates from the Internet, we need a valid IP address for it:

{{Note|if you use private IP for the VEcontainer, you have to set up NAT as described in [[Using NAT for VE container with private IPs]].}}

==== Setting DNS server for VE the container ====For the [[VEcontainer]] to be able to download updates from the Internet, we also need to specify a DNS for it:

==== Starting VE container ====Now start the VEcontainer:

You have to do some things in order to modify the installation to better suit the environment it will be run in (i.e. a VEcontainer).

First, enter a VEcontainer:

{{Warning|Do not run the commands below on the hardware node, they are only to be run within the VEcontainer!}} 

Some packages does not make sense in a VEcontainer, or are really optional. Remove those:

[VEcontainer]# dpkg -P ubuntu-minimal wpasupplicant wireless-tools \

console-terminus busybox-initramfs libvolume-id0\ ntpdate eject libasound2 pciutils tasksel tasksel-data \ laptop-detect {{Note|On removing the deb-package "module-init-tools", a fake-modprobe is needed for IPv6 addresses, see below!}}

[VEcontainer]# rm -fr /lib/udev

On a usual Linux system, <code>getty </code> is running on a virtual terminals, which a VE container does not have.So, having <code>getty</code> running doesn't make sense; more to say, it complains it can not open terminal device and this clutters the logs. So, first of all we stop all <code>getty</code> processes:  [container]# initctl stop tty{1,2,3,4,5,6}

There are Next, we disable running <code>getty</code>. This can be done in two ways to disable it:

[VEcontainer]# rm /etc/event.d/tty* 

[VEcontainer]# dpkg -P system-services

Second way can be dangerous for future versions of <code>system-services</code>, but it's OK for now since the only service they carry is running gettys<code>getty</code>s.

[VEcontainer]# chmod 700 /root

[VEcontainer]# usermod -L root ==== "fake-modprobe" needed for IPv6 addresses ====  [container]# ln -s /bin/true /sbin/modprobe <small>On setup IPv6, the command "modprobe -Q IPv6" is called, which fails without the "fake-modprobe"</small>

[VEcontainer]# apt-get update && apt-get upgrade

[VEcontainer]# apt-get install ssh quota

This is only useful if you installed SSH above. Each individual [[VEcontainer]] should have its own pair of SSH host keys. The code below will wipe out the existing SSH keys and instruct the newly-created [[VEcontainer]] to create new SSH keys on first boot.

<pre>[VEcontainer]# sed -i -e 's@\([[:space:]]\)\(/var/log/\)@\1-\2@' /etc/syslog.conf</pre>

[VEcontainer]# rm -f /etc/mtab [VEcontainer]# ln -s /proc/mounts /etc/mtab

[VEcontainer]# update-rc.d -f mtab.sh remove ==== Disable some services ==== In most of the cases you don't want klogd to run -- the only exception is if you configure iptables to log some events -- so you can disable it:  [container]# update-rc.d -f klogd remove

==== Get rid of tmpfs mounts Hostname ====Set proper hostname: [container]# echo "localhost" > /etc/hostname

[VE]# sed -ie '/tmpfs/d' ==== Set /etc/init.d/mountkernfs.shhosts ====

[container]# echo "127.0.0.1 localhost.localdomain localhost" > /etc/hosts ==== Disable some services Add ptys to /dev ==== This is needed in case /dev/pts will not me mounted after container start. In case /dev/ttyp* and /dev/ptyp* files are present, and LEGACY_PTYS support is enabled in the kernel, vzctl will still be able to enter container.  [container]# cd /dev && /sbin/MAKEDEV ptyp

Remove DNS entries: [VEcontainer]# update-rc> /etc/resolv.d -f klogd removeconf

[VEcontainer]# apt-get clean ==== Cleaning up log files ====  [container]# cd /var/log [container]# > messages; > auth.log; > kern.log; > bootstrap.log [container]# > dpkg.log; > syslog; > daemon.log; > apt/term.log [container]# rm -f *.0 *.1 ==== Anything else? ==== Think of what else could be done to better suit your needs. ==== Exit from the container ====