This guide tells how to install the kernel and the tools on [http://www.debian.org Debian] stableEtch or Lenny/Squeeze.  For Squeeze, use the Lenny directions. For Wheezy (7.0), use the vzctl package included in wheezy, together with the Wheezy OpenVZ kernels from [http://download.openvz.org/debian/ http://download.openvz.org/debian/]. Alternatively reduced functionality may be possible using the stock Debian Wheezy kernel (based on kernel.org version 3.2) and [[Vzctl_for_upstream_kernel]]. You may also wish to check the information on [http://wiki.debian.org/OpenVz the Debian wiki]. For Etch users, this document explains how to partially upgrade to Debian Lenny and install from lenny repositories ('''use this options at your risk''').

It is 's recommended to that you use a separate partition for container privatedirectories (by default <code>/var/lib/vz/private/<CTID></code>). The reason why you should do so for this is that if you wish to use the OpenVZ per-container disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind that "per-container quota " in this context includes not only pure per-container quota but also the usual Linux disk quota used in container, not on the [[HN]]. At the very least try to avoid using the root partition for containers, because the root user of a container will be able to overcome the 5% disk space barrier in some situations. If the HN root partition is completely filled, it will break the system.

At least try OpenVZ per-container disk quota is supported only for ext2/ext3 filesystems; therefore it makes sense to avoid using root partition for containers because the root user use one of these filesystems (ext3 is recommended) if you need per-container will be able to overcome the 5% disk space barrier in some situations. If the HN root partition is completely filled, it will break the systemquota.

OpenVZ per-container disk quota is supported === Repository setup (Etch only for ext2/ext3 filesystems so use one of these filesystems (ext3 is recommended) if you need per-container disk quota.===

'''If you are using Debian Lenny, this step in no longer required. Openvz kernel packages and tools are available on main repository.''' === Repository setup = 1. Using openvz.org repositories ====

This can be achieved by done via the following commands, as root or as privileged "sudo" user

==== 2. Using Debian repositories (upgrade to lenny) ==== There is even an a '''lenny''' repository with kernel 2.6.2428. '''Use it at your own risk!''' Add lenny repositories to your '''/etc/apt/sources.list'''<pre>deb http://DEBIAN-MIRROR/debian/ testing maindeb http://DEBIAN-MIRROR/debian-security/ testing/updates main</pre> Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:<pre>APT::Cache-Limit "100000000";</pre> Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:

# echo Package: *Pin: release a=etchPin-e "\ndeb httpPriority: 700 Package: *Pin://download.openvz.org/debian-systs release a=lenny openvz" >> /etc/apt/sources.list# wget Pin-q httpPriority://download.openvz.org/debian-systs/dso_archiv_signing_key.asc -O- | apt-key add - && apt-get update650

===== Configuring the bootloader =====

=== Rebooting into OpenVZ kernel === {{Warning|Before you restart your Server, keep in mind, that your system has all needed modules enabled; booting from your harddisk (e.g. hardware modules, raid system(s), lvm2 etc). May you need a INITRD (initramdisk) or compile needed kernel modules statically in.}} Now reboot the machine and choose the OpenVZ Linux Kernel on the boot loader menu. If the OpenVZ kernel has been booted successfully, proceed to installing Installing the user-level tools for OpenVZ. == Installing the user-level tools ===

{{Note|vzctl version from debian-systs, automate changing automatically inserts these options at the last of <tt>/etc/sysctl options .conf</tt>, except for openvznet.ipv4.ip_forward}}

net.ipv4.conf.default.proxy_arp = 0

net.ipv4.conf.all.rp_filter = 1

kernel.sysrq = 1

#net.ipv4.tcp_ecn = 0

net.ipv4.conf.default.send_redirects = 1net.ipv4.conf.all.send_redirects = 0

# [sudo] ln -s /var/lib/vz /vz

Precreated templates can be found [http://wiki.openvz.org/Download/template/precreated here] and [http://download.openvz.org/contrib/template/precreated/ here].

[[Debian template creation]], [[Ubuntu Gutsy template creation]] and [[:Category:Templates]].

# [sudo] apt-get install vzctl-ostmpl-debian-5.0-i386-minimal

After installing the OpenVZ kernelOn Debian squeeze, user tools and a minimal OS templateto create a first container and do some[[basic operations vzdump seems packaged in OpenVZ environment]]standard aptline. Read the For lenny, See [[download:doc/OpenVZ-Users-Guide.pdfBackup_of_a_running_container_with_vzdump]], browse this wiki.

That is not so! Although webmin shows that iptables If you want to secure your container with individual firewall rules (Linux Firewallinstead or additionally to securing the host node) is active then you must run iptables inside the container. This works slightly different than on boot, it is nota physical server. You need to So make a startup script for sure that you check that iptables rules are indeed applied as described further downexpected inside the container.

Now see what rules are already configuredAdd the following line into vz.conf to activate the respective iptables modules for all containers. Issue this command inside your container:

iptables -LIPTABLES="ip_tables ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_LOG ipt_conntrack ipt_helper ipt_state iptable_nat ip_nat_ftp ip_nat_irc ipt_TOS"

The output will be similar to this[[http://wiki.debian.org/DebianFirewall][Configure]] your iptable rules inside the container.

=== New nano /etc/network/if-pre-up.d/iptables rules ===

Let's tighten that up a bit by creating a test iptables fileAdd these lines to it:

nano #!/bin/bash /sbin/iptables-restore < /etc/iptables.testup.rules

In this The file enter some basic rulesneeds to be executable so change the permissions:

*filterchmod +x /etc/network/if-pre-up.d/iptables

# Accepts all established inbound connections -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT/etc/init.d/iptables start

# Allows HTTP and HTTPS connections from anywhere (Check inside the normal ports for websites) -A INPUT -p tcp --dport 80 -j ACCEPT -A INPUT -p tcp --dport 443 -j ACCEPT  # Allows SSH connections for script kiddies # THE -dport NUMBER IS THE SAME ONE YOU SET UP IN THE SSHD_CONFIG FILE -A INPUT -p tcp -m state --state NEW --dport 30000 -j ACCEPT  # Now you should read up on container that your iptables rules and consider whether ssh access # for everyone is really desired. Most likely you will only allow access from certain IPs.  # Allow ping -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT  # log iptables denied calls (access via 'dmesg' command) -A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7  # Reject all other inbound - default deny unless explicitly allowed policy: -A INPUT -j REJECT -A FORWARD -j REJECT  COMMIT That may look complicated, but look at each section at a time. You will see that it simply shuts all ports except the ones we have allowed - which in this case are ports 80 and 443 (the standard web browser ports) and the SSH port defined earlier. Activate these new rules:  iptables-restore < /etc/iptables.test.rules And see the differenceindeed applied:

Now If the output tells us that only rules do not show up as you would expect on a physical server then you might not have activated the ports defined above are open. All the others are closedneeded iptables modules.

iptables-save > # [sudo] /etc/iptablesinit.up.rulesd/vz start

To This does not make sure the iptables rules are started on a reboot we'll create a new filevz system automatically start at boot time. For automatic start:

nano /etc/network/if# [sudo] update-pre-uprc.d/iptablesvz defaults 98

Add these lines to == Use it:! ==

#!/bin/bashAfter installing the OpenVZ kernel, user tools and a minimal OS template /sbin/iptables-restore < /etc/iptablesto create a first container and do some [[basic operations in OpenVZ environment]].up.rules The file needs to be executable so change Read the permissions[[download:  chmod +x doc/etc/network/ifOpenVZ-preUsers-upGuide.pdf]], browse this wiki.d/iptables