OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Gentoo template creation

2006-10-13T14:02:09Z

Rtanner: /* Edit /etc/init.d/checkroot */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to be mounted at the boot time.

===Edit inittab===

Edit <code>/vz/private/777/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /vz/private/777/etc/init.d/checkroot
#!/sbin/runscript
depend()
{
echo
}
start()
{
echo
}
end()
{
echo
}
</pre>

===Edit /sbin/rc===

Comment line number 141 in /vz/private/777/sbin/rc:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter a VE:

<pre>
cd /vz/private/777/lib
rm udev-state/devices.tar.bz2
mknod udev/devices/ttyp0 c 3 0
mknod udev/devices/ptyp0 c 2 0
mknod udev/devices/ptmx c 5 2
</pre>
Set RC_DEVICES="static" in /vz/private/777/etc/conf.d/rc

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

{{Note|you have to <code>umount /vz/root/777/usr/portage/distfiles</code> before trying to stop your VE.}}

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]

Gentoo template creation

2006-08-15T07:39:22Z

Rtanner: /* Set up udev */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to be mounted at the boot time.

===Edit inittab===

Edit <code>/vz/private/777/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /vz/private/777/etc/init.d/checkroot
#!/sbin/runscript
depend()
{
}
start()
{
}
end()
{
}
</pre>

===Edit /sbin/rc===

Comment line number 141 in /vz/private/777/sbin/rc:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter VPS:

<pre>
cd /vz/private/777/lib
rm udev-state/devices.tar.bz2
mknod udev/devices/ttyp0 c 3 0
mknod udev/devices/ptyp0 c 2 0
mknod udev/devices/ptmx c 5 2
</pre>
Set RC_DEVICES="static" in /vz/private/777/etc/conf.d/rc

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]

Gentoo template creation

2006-08-15T07:36:00Z

Rtanner: /* Set up udev */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to be mounted at the boot time.

===Edit inittab===

Edit <code>/vz/private/777/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /vz/private/777/etc/init.d/checkroot
#!/sbin/runscript
depend()
{
}
start()
{
}
end()
{
}
</pre>

===Edit /sbin/rc===

Comment line number 141 in /vz/private/777/sbin/rc:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter VPS:

<pre>
cd /vz/private/777/lib
rm udev-state/devices.tar.bz2
mknod udev/devices/ttyp0 c 3 0
mknod udev/devices/ptyp0 c 2 0
mknod udev/devices/ptmx c 5 2
</pre>

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]

Gentoo template creation

2006-08-15T07:33:10Z

Rtanner: /* Edit /sbin/rc */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to be mounted at the boot time.

===Edit inittab===

Edit <code>/vz/private/777/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /vz/private/777/etc/init.d/checkroot
#!/sbin/runscript
depend()
{
}
start()
{
}
end()
{
}
</pre>

===Edit /sbin/rc===

Comment line number 141 in /vz/private/777/sbin/rc:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter VPS:

<pre>
rm /lib/udev-state/devices.tar.bz2
mknod /lib/udev/devices/ttyp0 c 3 0
mknod /lib/udev/devices/ptyp0 c 2 0
mknod /lib/udev/devices/ptmx c 5 2
</pre>

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]

Gentoo template creation

2006-08-15T07:31:15Z

Rtanner: /* Edit /etc/init.d/checkroot */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to be mounted at the boot time.

===Edit inittab===

Edit <code>/vz/private/777/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /vz/private/777/etc/init.d/checkroot
#!/sbin/runscript
depend()
{
}
start()
{
}
end()
{
}
</pre>

===Edit /sbin/rc===

Comment line number 141:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter VPS:

<pre>
rm /lib/udev-state/devices.tar.bz2
mknod /lib/udev/devices/ttyp0 c 3 0
mknod /lib/udev/devices/ptyp0 c 2 0
mknod /lib/udev/devices/ptmx c 5 2
</pre>

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]

Gentoo template creation

2006-08-15T07:30:20Z

Rtanner: /* Edit inittab */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to be mounted at the boot time.

===Edit inittab===

Edit <code>/vz/private/777/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /etc/init.d/checkroot
#!/sbin/runscript
depend()
{
}
start()
{
}
end()
{
}
</pre>

===Edit /sbin/rc===

Comment line number 141:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter VPS:

<pre>
rm /lib/udev-state/devices.tar.bz2
mknod /lib/udev/devices/ttyp0 c 3 0
mknod /lib/udev/devices/ptyp0 c 2 0
mknod /lib/udev/devices/ptmx c 5 2
</pre>

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]

Gentoo template creation

2006-08-15T07:29:36Z

Rtanner: /* Edit /etc/fstab */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to be mounted at the boot time.

===Edit inittab===

Edit <code>/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /etc/init.d/checkroot
#!/sbin/runscript
depend()
{
}
start()
{
}
end()
{
}
</pre>

===Edit /sbin/rc===

Comment line number 141:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter VPS:

<pre>
rm /lib/udev-state/devices.tar.bz2
mknod /lib/udev/devices/ttyp0 c 3 0
mknod /lib/udev/devices/ptyp0 c 2 0
mknod /lib/udev/devices/ptmx c 5 2
</pre>

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]

Gentoo template creation

2006-08-15T07:29:06Z

Rtanner: /* Make /etc/mtab a symlink to /proc/mounts */

This page is about making a template cache for OpenVZ VE from Gentoo Linux. The method is basically the same as described in [[Slackware template creation]] article.

===Download stage3===

We shall make the template from stage3 file. OpenVZ OS template should be an archive of root of the working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: http://www.gentoo.org/main/en/mirrors.xml.

===Create directory for the new VE and unarchive stage3 ===

<pre>
mkdir /vz/private/777
tar -xjf /root/stage3-i686-2006.0.tar.bz2 -C /vz/private/777
</pre>

===Create VE config===
Now you need to create the configuration file for the VE, 777.conf:

<pre>
vzctl set 777 --applyconfig vps.basic --save
</pre>

===Edit config===

Add to the /etc/vz/conf/777.conf:
<pre>
DISTRIBUTION="gentoo"
OSTEMPLATE="gentoo"
</pre>

===Make /etc/mtab a symlink to /proc/mounts===
The VE root filesystem is mounted by the host system, not the guest -- and therefore root fs will not appear in /etc/mtab. It will lead to df command non-working.
<pre>
rm -f /vz/private/777/etc/mtab
ln -s /proc/mounts /vz/private/777/etc/mtab
</pre>
After replacing /etc/mtab with a symlink to /proc/mounts, you will always have up-to-date information of what is mounted in /etc/mtab.

===Edit /etc/fstab===

<pre>
echo "proc /proc proc defaults 0 0" > /vz/private/777/etc/fstab
</pre>

We need only <code>/proc</code> to mounted at the boot time.

===Edit inittab===

Edit <code>/etc/inittab</code>, putting a hashmark (#) before the lines containing:

<pre>c?:1235:respawn:/sbin/agetty 38400 tty? linux</pre>

This prevents from starting <code>getty</code> and login.

===Edit /etc/shadow===

Edit <code>/vz/private/777/etc/shadow</code>, change root's password in the first line to an exclamation mark (!):

<pre>root:!:10071:0:::::</pre>

This will disable the root login until the password changed with <code>vzctl set VEID --userpasswd root:password</code>.

===Edit /etc/init.d/checkroot===

We have to clean this script and make them dummy, because we don't need mount or check root.

<pre>
cat > /etc/init.d/checkroot
#!/sbin/runscript
depend()
{
}
start()
{
}
end()
{
}
</pre>

===Edit /sbin/rc===

Comment line number 141:

<pre>try mount -n ${mntcmd:--t sysfs sysfs /sys}</pre>

This prevents from attepting to mount <code>/sys</code>.

===Set up udev===

Delete /lib/udev-state/devices.tar.bz2 and create some device nodes needed to enter VPS:

<pre>
rm /lib/udev-state/devices.tar.bz2
mknod /lib/udev/devices/ttyp0 c 3 0
mknod /lib/udev/devices/ptyp0 c 2 0
mknod /lib/udev/devices/ptmx c 5 2
</pre>

===Test===

<pre>
vzctl start 777
vzctl enter 777
</pre>

You can check running services.

<pre>
rc-status -a
</pre>

All services in boot and default runlevels must be started. If everything all right, stop it

<pre>
vzctl stop 777
</pre>

===Make distfiles and portage tree of the host system available in a VE===

To install software into a VE with portage you should mount /usr/portage into VE with "bind" option. Do this after VE starts:

<pre>
mkdir /vz/root/777/usr/portage
mount -o bind /usr/portage /vz/root/777/usr/portage
</pre>

If your /usr/portage/distfiles placed on the other partition do:

<pre>
mount -o bind /usr/portage/distfiles /vz/root/777/usr/portage/distfiles
</pre>

Now, to install package into a VE you just need enter there by <code>vzctl enter</code> and run

<pre>
emerge package_name
</pre>

while you have all the needed files in the <code>/usr/portage/distfiles</code> of host system.

For security reasons hold this directories mounted only while you are installing software into a VE.

===Create the cache file===

<pre>
cd /vz/private/777/
tar czf /vz/template/cache/gentoo.tar.gz *
</pre>

===Test the new cache file===

<pre>
vzctl create 800 --ostemplate gentoo --ipadd 192.168.0.10 --hostname testvps
</pre>

If created successfully, try to start it:

<pre>
vzctl start 800
</pre>

If it started, and you can ssh in, congratulations, you've got a working Gentoo template!

[[Category: HOWTO]]
[[Category: Templates]]