Open main menu

OpenVZ Virtuozzo Containers Wiki β

Changes

Talk:Debian template creation

1,499 bytes added, 15:13, 1 December 2013
Path for Lenny now in archive
== 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 {{unsigned|Juggler|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. --[[User:Kir|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 one command missing in a wrong path statement used for the instructions for debianpackages.
When I came to
<code>vzctl start 777</code>
I received the message
<precode>Starting VE ...VE private area /var/lib/vz/private/777 does not exist</code> 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. --[[User:Dusty|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<pre> # ln -s /var/lib/vz /vz</pre>
After some researches at the forum I and the wiki I found out that the step == Update document for Debian Etch ==<code>vzctl create 777 --ostemplate debian-3.1-i386-minimal</code> as described in the "OS template cache preparation" is missing in the debian specific sectionUpdated.
Because my knowlege about the system I'm not sure how to fit it in, but if your hardware node is very smallDebian Etch, I you don't want have to change 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 article by myselfSSH package.
20
edits