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 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'', specify it explicitly:* for AMD64/x86_64, use <code>amd64</code>* for IA64, use <code>ia64</code>* for i386 <code>i386</code>

Substitute your architecture instead of ''ARCH''. For example, for AMD64=== Preparing/x86_64, use <code>amd64</code> or for ia64, use <code>ia64</code>. For i386 you do not have to give this option.starting a container ===

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

Now then you have {{Note|an installation created by debootstrap, you can run it as alternative way is using chroot instead of running a VEcontainer. In the example below VE ID of 777 This is used; not recommended because of course you can use any other non-allocated IDsecurity concerns.}}

==== Moving installation to VE container private area ====

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

# mkdir /vz/private/777 # 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 \

ntpdateeject 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!}} Note that the above list of packages may be too extensive. Say, if you want to use <code>tasksel</code> tool, do not remove it — but then you have to let laptop-detect stay.

[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:

There are [container]# initctl stop tty{1,2,3,4,5,6} 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 ==== Hostname ====Set proper hostname: [container]# echo "localhost" > /etc/hostname ==== Set /etc/hosts ====  [container]# echo "127.0.0.1 localhost.localdomain localhost" > /etc/hosts

==== Get rid of tmpfs mounts Add ptys to /dev ====

[VE]# sed -ie 'This is needed in case /tmpfsdev/d' pts will not me mounted after container start. In case /etcdev/init.dttyp* and /dev/mountkernfsptyp* files are present, and LEGACY_PTYS support is enabled in the kernel, vzctl will still be able to enter container.sh

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

[VEcontainer]# apt-get clean ==== Cleaning up log files ====

Remove DNS entries: [VE]# > /etc/resolvThink of what else could be done to better suit your needs.conf

[container]# exit == Preparing for and packing template cache == The following commands are to be run in the host system (i.e. not inside a container). We don't need an IP for the container anymore, and we definitely do not need it in template cache, so remove it: [HW]# vzctl set 777 --ipdel all --save Stop the container: [HW]# vzctl stop 777 Change dir to the container private: [HW]# cd /vz/private/777 Now create a cached OS tarball. In the command below, you'll want to replace <arch> with your architecture (i386, amd64, ia64, etc). '''Note the space and the dot at the end of the command'''. [HW]# tar --numeric-owner -czf /vz/template/cache/ubuntu-7.10-<bigarch>-minimal.tar.gz . Look at the resulting tarball to see its size is sane: # ls -lh /vz/template/cache -rw-r--r-- 1 root root 53M Nov 15 12:40 ubuntu-7.10-i386-minimal.tar.gz == Testing template cache ==We can now create a container based on the just-created template cache. Be sure to change <bigtt>To be continuedi386</bigtt>to your architecture just like you did when you named the tarball above. [HW]# vzctl create 123456 --ostemplate ubuntu-7.10-<arch>-minimal Now make sure that your new container it works: [HW]# vzctl start 123456 [HW]# vzctl exec 123456 ps axf You should see that a few processes are running. Other tests that could be done are: [HW]# vzctl enter 123456 [container]# ps axf [container]# mount [container]# dpkg -l [container]# logout [HW]# Feel free to do more tests. == Final cleanup ==Stop and remove the test container you just created: [HW]# vzctl stop 123456 [HW]# vzctl destroy 123456 [HW]# rm -f /etc/vz/conf/123456.conf.destroyed Finally, let's remove the container we used for OS template cache creation: [HW]# vzctl destroy 777 [HW]# rm -f /etc/vz/big>conf/777.conf.destroyed == Updating the template cache == See [[Updating Ubuntu template]]