2,253
edits
Changes
m
Robot: Automated text replacement (-VE +container)
This page is about making a template cache for OpenVZ [[VEcontainer]] from Slackware linux.
(This method was used for creating the minimal cache from Slackware 10.2)
The method is basically the same as described in article [[Debian template creation]].
=== Downloading and installing Slackware ===
First you need to download Slackware linux from [http://www.slackware.org/getslack/ http://www.slackware.org/getslack/]. Then you have to [http://www.slackware.org/install/ install] it to some hardware you can spare while the cache creation process is going on. For [[VEcontainer]] creation it is recommended not to install any unnecessary software into the box you are making the cache from.
This means for a minimal Slackware 10.2 cache I have chosen only series A (<tt>Base Linux System</tt>) at the package series selection screen of Slackware Setup. Then '''expert''' prompting mode on the next screen. On the Series A package selection screen I chose the following packages:
* dcron
* devs
* e2fsprogs <i>- This is not really needed for a VEcontainer, but let him install it</i>
* elvis
* etc
After selecting these packages just install the kernel and lilo, you are ready to run Slackware!
=== Configuring Slackware for acting as a VE container ===
Now that you have a running minimal Slackware installation, You can begin to prepare it to be
a template for a [[VEcontainer]]. First you need some additional packages, 7 exactly:
{| class="wikitable"
</pre>
After these steps, you are ready to move your Slackware installation into a [[VEcontainer]].
=== Moving a Slackware installation into a VE container ===
I did it by compressing the whole filesystem into a tgz file and copying it to the host running OpenVZ.
</pre>
== Preparing the new VE container ==
=== Creating VE container config ===
Now you need to create the configuration file for the [[VEcontainer]], 777.conf:
<pre>
</pre>
=== Getting the filesystem ready to run in a VE container ===
Now you need to make some minor alterations under the /vz/private/777 directory.
rm /vz/private/777/etc/ssh/*key*
</pre>
This will ensure that a unique ssh key is generated for every single [[VEcontainer]] at the first boot.
Edit ssh_config and sshd_config here if you want.
{{Note|if you are going to use iptables rules inside your Slackware containers which will do logging (i.e. the ones with the <tt>LOG</tt> target), you should not disable <tt>klogd</tt>.}}
== Testing the new VE container and making a cache file ==
=== Testing the new VE container ===
To test the new [[VEcontainer]], simply start it:
<pre>
vzctl start 777
</pre>
If you did everything all right (and this article is correct) your new Slackware [[VEcontainer]] will boot.
If the VE container booted, and you can enter/ssh to it, then stop it:
<pre>
vzctl stop 777
=== Making a cache file ===
Now make a .tar.gz out of the [[VEcontainer]]:
<pre>
tar czf /vz/template/cache/slackware-10.2-i486-minimal.tar.gz /vz/private/777/
