<p>Indeed there is a specific set of actions to be performed on a newly created container which is to be used to make a template. This includes:<br>
- log files truncation;<br>
- yum/apt database cleanup;<br>
- adjustments to cron jobs and init.d services;<br>
- making sure ssh keys are unique (this is specific to Debian, maybe Ubuntu -- they generate key pairs on SSH package installation not the first run);<br>
- disabling root login (usermod -L root should be sufficient, although it's always better to check);<br>
- removing getty entries from inittab (or its upstart/systemd analog) — since there are no terminals in CT;<br>
- making sure syslogd don't do sync () for each log line written (this ruins I/O performance if you have tens or hundreds of CTs);<br>
- proper software repository configuration;<br>
- (optional) removal of unneeded packages (like kernel) just for the sake of disk space savings (this is usually done by creating stub "dummy" packages that virtually provide the stuff required by other packages but not really needed;<br>
- (optional) removal of some extra stuff like locale data;<br>
- linking /etc/mtab to /proc/mounts (although it might not be needed);<br>
- something else I can't remember at the moment.</p>
<p>Then, some things are performed by vzctl's postcteate.sh script which is run during vzctl create. This, among other things, include crontab times randomization, to prevent all CTs to run say cron.daily jobs at the same time.</p>
<p>Hope that helps,<br>
Kir.</p>
<p>--<br>
Sent from my Android phone</p>
<div class="gmail_quote">On Sep 15, 2011 12:57 AM, "Kelvin Raywood" <<a href="mailto:kray@triumf.ca">kray@triumf.ca</a>> wrote:<br type="attribution">> Scott Dowdle wrote:<br>>> ...<br>>> The final products are a i386 and an x86_64 contributed SL 5.7 OS Template.<br>
> <br>> Thanks very much for these Scott. This is much appreciated.<br>> <br>> I just wanted to mention one thing that I got bitten by recently with a <br>> template from contrib.<br>> <br>> In the official templates, /etc/shadow has * in the encrypted-password <br>
> field for root so that you can't login as root using a password.<br>> In April, an early SL-6.0 template was contributed <br>> (scientificlinux-6.0-x86.tar.gz Apr-11-2011) which has an encrypted <br>> password string for root.<br>
> <br>> We normally disable password access to root in /etc/ssh/sshd_config via <br>> "PermitRootLogin without-password" and use ssh keys or "vzctl enter" to<br>> get root access so didn't notice that the machine had a root password <br>
> enabled. Also, since it was our first SL-6 container, we didn't have <br>> our deployment procedure sorted out properly and this was the <br>> sshd_config part.<br>> <br>> It didn't take long for some spider to find the machine and guess the <br>
> password. An IRC robot was installed and /root/.ssh/authorized_keys was <br>> overwritten. We noticed fairly quickly and then cracked the password <br>> string.<br>> <br>> Anyway, we learned our lesson but I think it would also be good practice <br>
> for contributors to check that their template does not have a root password.<br>> <br>> Oh yeah - the cracked password ... password<br>> <br>> --<br>> Kel Raywood<br>> TRIUMF<br>> Vancouver BC<br>
> <br>> _______________________________________________<br>> Users mailing list<br>> <a href="mailto:Users@openvz.org">Users@openvz.org</a><br>> <a href="https://openvz.org/mailman/listinfo/users">https://openvz.org/mailman/listinfo/users</a><br>
</div>