OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Talk:Shared webhosting

2011-11-15T19:54:45Z

RobFantini: /* MySQL Socket Sharing */

== Sharing mysql socket ==
Wouldn't it be easier to just link the directory containing the socket using 'mount --bind'? Don't think that inode will change. [[Special:Contributions/62.195.200.207|62.195.200.207]] 16:39, 15 July 2011 (UTC)

== Linking to howto pages ==
I probably did something stupid, but how can I link from the HOWTO's to this page?
--[[User:Hvdkamer|Hvdkamer]] 08:23, 2 August 2006 (EDT)
: If you want to link to the Category:HOWTO, you put it like this
: <code><nowiki>[[:Category:HOWTO HOWTOs (i.e. this is link text)]]</nowiki></code>
: If you want your article to be included into HOWTO category, you put it like this (in any part of the article, usually at the end):
: <code><nowiki>[[Category:HOWTO]]</nowiki></code>
: --[[User:Kir|Kir]] 09:51, 2 August 2006 (EDT)

== Rename? ==

I suggest renaming the article to something like "Application separation" or "Services separation" since this is what you actually describe :) --[[User:Kir|Kir]] 10:22, 2 August 2006 (EDT)

: Go ahead if you think it describes the content better. I started to investigate OpenVZ because I had serious problems with shared hosting. The minimal servers (it is only a rough draft at this moment) are the solution to that. You could see this as application seperation, but for the end-user it is a "normal" webhosting account. Only he/she can do much more and can not break his/her prison :-) --[[User:Hvdkamer|Hvdkamer]] 10:28, 2 August 2006 (EDT)

:: May be to explain better my choice. After some serious problems with PHP (users who knew where an include with passwords lived, could see the content) I started to investigate the option of Apache threads with its own user credentials. That was the abonded project perchild. So there is not an easy technical solution. Also users hate safe_mode and open_basedir because it breaks there applications. They also want obscure CGI-scripts and all the things we administrators hate. I already used chrooted OpenSSH shell accounts. With the minimal servers I take that one step further. Now every user has total control (he/she can even be root) over his/her space.

:: If I had to do my research again, I think I would still start with "shared webhosting". Not "application seperation". I think that my term, although not exactly correct, will draw more people to this site. I think of it as "user seperation", but that is the whole point of OpenVZ? As said, its your Wiki, so change it if you think it is better :-) --[[User:Hvdkamer|Hvdkamer]] 10:40, 2 August 2006 (EDT)

::: I changed the introduction to give some examples of the problems shared webhosting is facing. I think that you now could see were it is going? I'm still in the process of setting up this server. So I thought to start this page while I'm working on it. Because if you do it weeks later, most subtle points are lost :-) --[[User:Hvdkamer|Hvdkamer]] 11:42, 2 August 2006 (EDT)

== Proxying ==

I would suggest using [http://www.apsis.ch/pound/ Pound] as the Proxy Server running on your Frontend VE. Its a pretty lightweight and _fast_ Proxy. Besides proxying it does also support load balancing, failover and SSL. I've been using it for various projects over the past few years, its proven to be pretty stable and reliable. --[[User:Torsten|Torsten]] 14:51, 9th Nov 2006 (CST)

== MySQL Socket Sharing ==

2011-11-15 I had this issue using mysql :
<pre>
Could not connect to database: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
111115 22:05:40 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address
111115 22:05:40 [ERROR] Do you already have another mysqld server running on port: 3306 ?
</pre>
changing bind-address in /etc/mysql/my.cnf from
bind-address = 127.0.0.1
to
bind-address = 10.100.100.220
fixed it for us. using ubuntu 11.10
------------

There's a good guide, using "mount --bind" available at http://sudhaker.com/2008/04/isolated-mysql-installation-openvz-cluster/, but I couldn't get it to work.
Also the "ln /var/lib/vz/private/101/var/run/mysqld/mysqld.sock ..." mentioned in the article itself does not work for me: the mysqld.sock only appears in /vz/root/123, not /vz/private/123.
Additionally, "mysql -u root -p -S /vz/root/123/var/run/mysqld/mysqld.sock" fails with:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/vz/root/1234/var/run/mysqld/mysqld.sock' (111)
This is with Ubuntu Hardy (fixed kernel from Git).
[[User:Blueyed|Blueyed]] 16:23, 28 April 2008 (EDT)

=== Decreased security ===
Isn't sharing sockets blocking advantages promoted in <blockquote>"As an extra security measure you can use the internal IP-address as well."</blockquote>
I'd actually would like to have mysql reject root user logins unless logging in from VE actually housing mysql server. That's impossible on using Unix sockets since it's always using "localhost" then, isn't it?

Talk:Download/kernel/2.6.32/2.6.32-belyayev.1

2010-06-07T03:09:02Z

RobFantini: Created page with 'thank you for the work you do, and the bundled history lesson.. there a little info at http://en.wikipedia.org/wiki/Pavel_Belyayev on Pavel Ivanovich Belyaev .'

thank you for the work you do, and the bundled history lesson.. there a little info at http://en.wikipedia.org/wiki/Pavel_Belyayev on Pavel Ivanovich Belyaev .

Bind mounts

2010-04-16T04:33:33Z

RobFantini: /* Read-only bind mounts */

Recent Linux kernels support an operation called 'bind mounting' which makes part of a mounted filesystem visible at some other mount point. See 'man mount' for more information.

Bind mounts can be used to make directories on the hardware node visible to the container.

== Filesystem layout ==
OpenVZ uses two directories. Assuming our container is numbered 777, these directories are:

* <code>VE_PRIVATE</code>: $VZDIR/private/777
* <code>VE_ROOT</code>: $VZDIR/root/777

{{Note|<code>$VZDIR</code> is usually <code>/vz</code>, on Debian systems however this is <code>/var/lib/vz</code>. In this document this is further referred to as <code>$VZDIR</code> -- substitute it with what you have.}}

<code>VE_PRIVATE</code> is a place for all the container files. <code>VE_ROOT</code> is the mount point to which <code>VE_PRIVATE</code> is mounted during container start (or when you run <code>vzctl mount</code>

{{Warning|If you want to do a bind mount for container, you need to '''use <code>VE_ROOT</code>''' (not <code>VE_PRIVATE</code>!) and '''make sure that container is mounted''' (this can be checked using <code>vzctl status</code>).}}

== Manual mount example ==

On the HN we have a directory <code>/home</code> which we wish to make available (shared) to container 777.

The correct command to issue on the HN is:

mount --bind /home $VZDIR/root/777/home

The container must be started (or at least mounted) and the destination directory must exist. The container will see this directory mounted like this:

# df
Filesystem 1K-blocks Used Available Use% Mounted on
simfs 10485760 298728 10187032 3% /
ext3 117662052 104510764 7174408 94% /home

During the container stop vzctl unmounts that bind mount, so you have to mount it again when you start the container for the next time. Luckily there is a way to automate it.

== Make the mount persistent ==

Put a mount script in OpenVZ configuration directory (<code>/etc/vz/conf/</code>) with the name <code>''CTID''.mount</code> (where <code>''CTID''</code> is container ID, like 777). This script will be executed every time you run <code>vzctl mount</code> or <code>vzctl start</code> for a particular container. If you need to the same for all containers, use the global mount script named <code>vps.mount</code>.

From any mount script you can use the following environment variables:
* <code>${VEID}</code> -- container ID (like <code>777</code>).
* <code>${VE_CONFFILE}</code> -- container configuration file (like <code>/etc/vz/conf/777.conf</code>)

Now, in order to get the value of <code>VE_ROOT</code> you need to source both the global OpenVZ configuration file, and then the container configuration file, in that particular order. This is the same way vzctl uses to determine <code>VE_ROOT</code>.

=== Mount script example ===
Here is an example of such a mount script (it can either be <code>/etc/vz/conf/vps.mount</code> or <code>/etc/vz/conf/''CTID''.mount</code>)
#!/bin/bash
source /etc/vz/vz.conf
source ${VE_CONFFILE}
mount -n --bind /mnt/disk ${VE_ROOT}/mnt/disk

=== Unmount script example ===
For unmounting a filesystem, <code>/etc/vz/conf/vps.umount</code> or <code>/etc/vz/conf/''CTID''.umount</code> script can be used in the same way:

#!/bin/bash
source /etc/vz/vz.conf
source ${VE_CONFFILE}
umount ${VE_ROOT}/mnt/disk

{{Note|<code>''CTID''.umount</code> script is not strictly required, since vzctl tries to unmount everything on CT stop. But you'd better have it anyway.}}

== Read-only bind mounts ==

Since Linux kernel 2.6.26, bind mounts can be made read-only. The trick is to first mount as usual, and then remount it read-only:

mount -n --bind /home $VZDIR/root/777/home
mount -n --bind -oremount,ro $VZDIR/root/777/home

== See also ==
* [[NFS]]
* [[FUSE]]
* [[Mounting filesystems]]

[[Category:HOWTO]]

Bind mounts

2010-04-16T04:33:07Z

RobFantini: /* Mount script example */

Recent Linux kernels support an operation called 'bind mounting' which makes part of a mounted filesystem visible at some other mount point. See 'man mount' for more information.

Bind mounts can be used to make directories on the hardware node visible to the container.

== Filesystem layout ==
OpenVZ uses two directories. Assuming our container is numbered 777, these directories are:

* <code>VE_PRIVATE</code>: $VZDIR/private/777
* <code>VE_ROOT</code>: $VZDIR/root/777

{{Note|<code>$VZDIR</code> is usually <code>/vz</code>, on Debian systems however this is <code>/var/lib/vz</code>. In this document this is further referred to as <code>$VZDIR</code> -- substitute it with what you have.}}

<code>VE_PRIVATE</code> is a place for all the container files. <code>VE_ROOT</code> is the mount point to which <code>VE_PRIVATE</code> is mounted during container start (or when you run <code>vzctl mount</code>

{{Warning|If you want to do a bind mount for container, you need to '''use <code>VE_ROOT</code>''' (not <code>VE_PRIVATE</code>!) and '''make sure that container is mounted''' (this can be checked using <code>vzctl status</code>).}}

== Manual mount example ==

On the HN we have a directory <code>/home</code> which we wish to make available (shared) to container 777.

The correct command to issue on the HN is:

mount --bind /home $VZDIR/root/777/home

The container must be started (or at least mounted) and the destination directory must exist. The container will see this directory mounted like this:

# df
Filesystem 1K-blocks Used Available Use% Mounted on
simfs 10485760 298728 10187032 3% /
ext3 117662052 104510764 7174408 94% /home

During the container stop vzctl unmounts that bind mount, so you have to mount it again when you start the container for the next time. Luckily there is a way to automate it.

== Make the mount persistent ==

Put a mount script in OpenVZ configuration directory (<code>/etc/vz/conf/</code>) with the name <code>''CTID''.mount</code> (where <code>''CTID''</code> is container ID, like 777). This script will be executed every time you run <code>vzctl mount</code> or <code>vzctl start</code> for a particular container. If you need to the same for all containers, use the global mount script named <code>vps.mount</code>.

From any mount script you can use the following environment variables:
* <code>${VEID}</code> -- container ID (like <code>777</code>).
* <code>${VE_CONFFILE}</code> -- container configuration file (like <code>/etc/vz/conf/777.conf</code>)

Now, in order to get the value of <code>VE_ROOT</code> you need to source both the global OpenVZ configuration file, and then the container configuration file, in that particular order. This is the same way vzctl uses to determine <code>VE_ROOT</code>.

=== Mount script example ===
Here is an example of such a mount script (it can either be <code>/etc/vz/conf/vps.mount</code> or <code>/etc/vz/conf/''CTID''.mount</code>)
#!/bin/bash
source /etc/vz/vz.conf
source ${VE_CONFFILE}
mount -n --bind /mnt/disk ${VE_ROOT}/mnt/disk

=== Unmount script example ===
For unmounting a filesystem, <code>/etc/vz/conf/vps.umount</code> or <code>/etc/vz/conf/''CTID''.umount</code> script can be used in the same way:

#!/bin/bash
source /etc/vz/vz.conf
source ${VE_CONFFILE}
umount ${VE_ROOT}/mnt/disk

{{Note|<code>''CTID''.umount</code> script is not strictly required, since vzctl tries to unmount everything on CT stop. But you'd better have it anyway.}}

== Read-only bind mounts ==

Since Linux kernel 2.6.26, bind mounts can be made read-only. The trick is to first mount as usual, and then remount it read-only:

mount --bind /home $VZDIR/root/777/home
mount --bind -oremount,ro $VZDIR/root/777/home

== See also ==
* [[NFS]]
* [[FUSE]]
* [[Mounting filesystems]]

[[Category:HOWTO]]

Debian sarge

2010-03-25T01:15:42Z

RobFantini:

* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info from http://wiki.openvz.org/Debian_template_creation I did this.

* note at the end I had to copy an existing .conf file to make this work. so the following needs improvement. I'll try to solve the issues and then edit this page. in the mean time if you need Sarge then this may be of some use.

aptitude install debootstrap

* I used '599' as the container number. of course you'd want to pick an unused number.

debootstrap --arch i386 sarge /var/lib/vz/private/599 http://archive.debian.org/debian

> /etc/vz/conf/599.conf

vzctl set 599 --applyconfig pve.auto --save
Saved parameters for CT 599

echo "OSTEMPLATE=debian-3.1" >> /etc/vz/conf/599.conf

vzctl set 599 --ipadd 10.100.100.144 --save

vzctl set 599 --nameserver 10.100.100.2 --save

<pre>
vzctl start 599

Starting container ...
Initializing quota ...
Container is mounted
Adding IP address(es): 10.100.100.144
Setting CPU units: 250
Configure meminfo: 7680
File resolv.conf was modified
Container start in progress...
</pre>

vzctl enter 599

* note. the container started and I could enter and work with it cron cli. however the vm was mis-configured from proxmox's web control pages' point of view. so i think this line needs a defferent template:
vzctl set 599 --applyconfig pve.auto --save

to solve the issue I copied a working Debian Etch conf file from /etc/vz/conf to 599 and made a few changes..

I'll look around to try to find a conf template to use ..

* this is my final working conf file. it works ok from teh web control page.
<pre>
# PVE default config for 256MB RAM

ONBOOT="yes"

# Primary parameters
NUMPROC="1024:1024"
NUMTCPSOCK="9223372036854775807:9223372036854775807"
NUMOTHERSOCK="9223372036854775807:9223372036854775807"
VMGUARPAGES="131072:9223372036854775807"

# Secondary parameters
KMEMSIZE="9223372036854775807:9223372036854775807"
OOMGUARPAGES="131072:9223372036854775807"
PRIVVMPAGES="131072:143572"
TCPSNDBUF="9223372036854775807:9223372036854775807"
TCPRCVBUF="9223372036854775807:9223372036854775807"
OTHERSOCKBUF="9223372036854775807:9223372036854775807"
DGRAMRCVBUF="9223372036854775807:9223372036854775807"

# Auxiliary parameters
NUMFILE="9223372036854775807:9223372036854775807"
NUMFLOCK="9223372036854775807:9223372036854775807"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="9223372036854775807:9223372036854775807"
LOCKEDPAGES="65536:65536"
SHMPAGES="9223372036854775807:9223372036854775807"
NUMIPTENT="9223372036854775807:9223372036854775807"
PHYSPAGES="0:9223372036854775807"

# Disk quota parameters
DISKSPACE="2097152:2306867"
DISKINODES="400000:440000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"

# CPU fair sheduler parameter
CPUUNITS="1000"
CPUS="1"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-3.1"
ORIGIN_SAMPLE="pve.auto"
IP_ADDRESS="10.100.100.145"
HOSTNAME="fbc145.fantinibakery.com"
NAMESERVER="10.100.100.2"
SEARCHDOMAIN="fantinibakery.com"
</pre>

[[Category: Debian]]

Debian sarge

2010-03-25T00:49:55Z

RobFantini:

* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info from http://wiki.openvz.org/Debian_template_creation I did this.

aptitude install debootstrap

* I used '599' as the container number. of course you'd want to pick an unused number.

debootstrap --arch i386 sarge /var/lib/vz/private/599 http://archive.debian.org/debian

> /etc/vz/conf/599.conf

vzctl set 599 --applyconfig pve.auto --save
Saved parameters for CT 599

echo "OSTEMPLATE=debian-3.1" >> /etc/vz/conf/599.conf

vzctl set 599 --ipadd 10.100.100.144 --save

vzctl set 599 --nameserver 10.100.100.2 --save

<pre>
vzctl start 599

Starting container ...
Initializing quota ...
Container is mounted
Adding IP address(es): 10.100.100.144
Setting CPU units: 250
Configure meminfo: 7680
File resolv.conf was modified
Container start in progress...
</pre>

vzctl enter 599

* note. the container started and I could enter and work with it cron cli. however the vm was mis-configured from proxmox's web control pages' point of view. so i think this line needs a defferent template:
vzctl set 599 --applyconfig pve.auto --save

to solve the issue I copied a working Debian Etch conf file from /etc/vz/conf to 599 and made a few changes..

I'll look around to try to find a conf template to use ..

* this is my final working conf file. it works ok from teh web control page.
<pre>
# PVE default config for 256MB RAM

ONBOOT="yes"

# Primary parameters
NUMPROC="1024:1024"
NUMTCPSOCK="9223372036854775807:9223372036854775807"
NUMOTHERSOCK="9223372036854775807:9223372036854775807"
VMGUARPAGES="131072:9223372036854775807"

# Secondary parameters
KMEMSIZE="9223372036854775807:9223372036854775807"
OOMGUARPAGES="131072:9223372036854775807"
PRIVVMPAGES="131072:143572"
TCPSNDBUF="9223372036854775807:9223372036854775807"
TCPRCVBUF="9223372036854775807:9223372036854775807"
OTHERSOCKBUF="9223372036854775807:9223372036854775807"
DGRAMRCVBUF="9223372036854775807:9223372036854775807"

# Auxiliary parameters
NUMFILE="9223372036854775807:9223372036854775807"
NUMFLOCK="9223372036854775807:9223372036854775807"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="9223372036854775807:9223372036854775807"
LOCKEDPAGES="65536:65536"
SHMPAGES="9223372036854775807:9223372036854775807"
NUMIPTENT="9223372036854775807:9223372036854775807"
PHYSPAGES="0:9223372036854775807"

# Disk quota parameters
DISKSPACE="2097152:2306867"
DISKINODES="400000:440000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"

# CPU fair sheduler parameter
CPUUNITS="1000"
CPUS="1"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-3.1"
ORIGIN_SAMPLE="pve.auto"
IP_ADDRESS="10.100.100.145"
HOSTNAME="fbc145.fantinibakery.com"
NAMESERVER="10.100.100.2"
SEARCHDOMAIN="fantinibakery.com"
</pre>

[[Category: Debian]]

Debian sarge

2010-03-25T00:47:24Z

RobFantini:

* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info from http://wiki.openvz.org/Debian_template_creation I did this.

aptitude install debootstrap

* I used '599' as the container number. of course you'd want to pick an unused number.

debootstrap --arch i386 sarge /var/lib/vz/private/599 http://archive.debian.org/debian

> /etc/vz/conf/599.conf

vzctl set 599 --applyconfig pve.auto --save
Saved parameters for CT 599

echo "OSTEMPLATE=debian-3.1" >> /etc/vz/conf/599.conf

vzctl set 599 --ipadd 10.100.100.144 --save

vzctl set 599 --nameserver 10.100.100.2 --save

<pre>
vzctl start 599

Starting container ...
Initializing quota ...
Container is mounted
Adding IP address(es): 10.100.100.144
Setting CPU units: 250
Configure meminfo: 7680
File resolv.conf was modified
Container start in progress...
</pre>

vzctl enter 599

* note. the container started and I could enter and work with it cron cli. however the vm was mis-configured from proxmox's web control pages' point of view. so i think this line needs a defferent template:
vzctl set 599 --applyconfig pve.auto --save

to solve the issue I copied a working Debian Etch conf file from /etc/vz/conf to 599 and made a few changes..

I'll look around to try to find a conf template to use ..

[[Category: Debian]]

Debian sarge

2010-03-25T00:30:49Z

RobFantini:

* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info from http://wiki.openvz.org/Debian_template_creation I did this.

aptitude install debootstrap

* I used '599' as the container number. of course you'd want to pick an unused number.

debootstrap --arch i386 sarge /var/lib/vz/private/599 http://archive.debian.org/debian

> /etc/vz/conf/599.conf

vzctl set 599 --applyconfig pve.auto --save
Saved parameters for CT 599

echo "OSTEMPLATE=debian-3.1" >> /etc/vz/conf/599.conf

vzctl set 599 --ipadd 10.100.100.144 --save

vzctl set 599 --nameserver 10.100.100.2 --save

<pre>
vzctl start 599

Starting container ...
Initializing quota ...
Container is mounted
Adding IP address(es): 10.100.100.144
Setting CPU units: 250
Configure meminfo: 7680
File resolv.conf was modified
Container start in progress...
</pre>

vzctl enter 599

[[Category: Debian]]

Debian sarge

2010-03-25T00:26:58Z

RobFantini:

* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info from http://wiki.openvz.org/Debian_template_creation I did this.

aptitude install debootstrap

* I used '599' as the container number. of course you'd want to pick an unused number.

debootstrap --arch i386 sarge /var/lib/vz/private/599 http://archive.debian.org/debian

> /etc/vz/conf/599.conf

vzctl set 599 --applyconfig pve.auto --save
Saved parameters for CT 599

echo "OSTEMPLATE=debian-3.1" >> /etc/vz/conf/599.conf

vzctl set 599 --ipadd 10.100.100.144 --save

vzctl set 599 --nameserver 10.100.100.2 --save

<pre>
vzctl start 599

Starting container ...
Initializing quota ...
Container is mounted
Adding IP address(es): 10.100.100.144
Setting CPU units: 250
Configure meminfo: 7680
File resolv.conf was modified
Container start in progress...
</pre>

vzctl enter 599

Debian sarge

2010-03-25T00:25:56Z

RobFantini:

* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info from http://wiki.openvz.org/Debian_template_creation I did this.

aptitude install debootstrap

* I used '599' as the container number. of course you'd want to pick an unused number.

debootstrap --arch i386 sarge /var/lib/vz/private/599 http://archive.debian.org/debian

> /etc/vz/conf/599.conf

vzctl set 599 --applyconfig pve.auto --save
Saved parameters for CT 599

echo "OSTEMPLATE=debian-3.1" >> /etc/vz/conf/599.conf

vzctl set 599 --ipadd 10.100.100.144 --save

vzctl set 599 --nameserver 10.100.100.2 --save

<pre>
vzctl start 599

Starting container ...
Initializing quota ...
Container is mounted
Adding IP address(es): 10.100.100.144
Setting CPU units: 250
Configure meminfo: 7680
File resolv.conf was modified
Container start in progress...
</pre>

vzctl enter 599

Debian sarge

2010-03-25T00:24:38Z

RobFantini: Created page with '* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info fr…'

* on proxmox-ve we need to run some Debian Sarge containers. we are using Proxmox Virtual Environment 1.5 . there are not any Sarge templates that I could find, so using info from http://wiki.openvz.org/Debian_template_creation I did this.

aptitude install debootstrap

debootstrap --arch i386 sarge /var/lib/vz/private/599 http://archive.debian.org/debian

> /etc/vz/conf/599.conf
vzctl set 599 --applyconfig pve.auto --save
Saved parameters for CT 599

echo "OSTEMPLATE=debian-3.1" >> /etc/vz/conf/599.conf

vzctl set 599 --ipadd 10.100.100.144 --save

vzctl set 599 --nameserver 10.100.100.2 --save

<pre>
vzctl start 599

Starting container ...
Initializing quota ...
Container is mounted
Adding IP address(es): 10.100.100.144
Setting CPU units: 250
Configure meminfo: 7680
File resolv.conf was modified
Container start in progress...
</pre>

vzctl enter 599