Talk:Debian template creation

Path for Lenny now in archive

Lenny (old release)

debootstrap --arch i386 lenny /vz/private/777 http://archive.debian.org/debian/

edit/symlink /etc/mtab, /proc/mounts

Does anybody have valuable information why this would make sense and if this is needed? http://wiki.openvz.org/Debian_template_creation#Fix_.2Fetc.2Fmtab —The preceding unsigned comment was added by Juggler (talk • contribs) 20:41, 13 February 2007.

Linking /etc/mtab -> /proc/mounts is needed since VE's root filesystem is actually mounted from the Hardware Node. Thus, there is no appropriate record in /etc/mtab, so utilities like df fail to work (since they get a list of mounts from the /etc/mtab). After linking /etc/mtab to /proc/mounts, /etc/mtab shows all the mounts, including the one for root filesystem, so df works fine. --Kir 10:25, 14 February 2007 (EST)

problem with path

Hi all, This is my first trial with openVZ and a wiki. Please give me some hints, if anything is wrong. Don't hesitate to correct my poor english.

I just installed openVZ on a rather old test box with Debian. Installation failed at first and I suppose there is a wrong path statement used for the debian packages.

When I came to vzctl start 777 I received the message Starting VE ... VE private area /var/lib/vz/private/777 does not exist

Moving the directory 777 from /vz/private to /var/lib/vz/private solves this problem.

Now I could start and enter the new VE. --(unsigned)

This isn't a very good place to ask for help. You should use the forum instead. See the link for the forum in the sidebar on the left. --Dusty 19:00, 9 April 2007 (EDT)

Debian template creation

For backward compablity to main OpenVZ:

Create a symlink from /var/lib/vz to /vz

 # ln -s /var/lib/vz /vz

Update document for Debian Etch

Updated.

I'm not sure how to fit it in, but if your hardware node is Debian Etch, you don't have to make a temporary VE to create a template. You can just chroot into it instead, which probably saves some hassle. It's probably not worth making a whole new page for it and it'd probably cause confusion to add it to this document. If someone knows what to do with that information, feel free to do something. I always just use a chroot because it's so much easier for me. But when I tried it on a RedHat box, it didn't quite work out for some interesting locale reason when installing the SSH package.