Installation on Virtuozzo containers for Windows

This section covers only the essential steps that must be taken to deploy Plesk inside Virtuozzo containers for Windows. Before proceeding with installation, please familiarize yourself with Virtuozzo containers documentation available at

Deploying Plesk in a Virtuozzo containers environment implies the following two stages:

  1. Installing the Plesk application template on a hardware node.
  2. Creating a Container and deploying the application from the template.

The first stage is performed on each hardware node only once: As soon as an application template is installed on a hardware node, it can be deployed to as many Containers as required.

Instead of creating a new Container every time you need to deploy a Container with Plesk, you can clone an existing Container where Plesk is installed, which acts as a sort of Template Container.


Note: If your operating system is Microsoft Windows 2008 and the container offline management is turned on, you can log in to Plesk by visiting https://host-name:8443/ or https://IP-address:8443/ and providing your local administrator credentials, or by visiting http://host-name:8880/ or http://IP-address:8880/ and providing global administrator credentials.


To install Plesk in Virtuozzo Containers for Windows:

  1. Obtain the Plesk template from the Virtuozzo website and upload it to the target Virtuozzo containers hardware node.
  2. Install application templates of Plesk by issuing a command of the following format:

    vzpkgdeploy [-q|-v] -i <template-file>


    • -q disables logging to the display and to the log file
    • -v sets the log level to the maximum possible value for this vzpkgdeploy session

    For example,

    vzpkgdeploy -i PANEL_10.0.0/20100804.10


To create a new Container and install Plesk into it:

  1. Create a container and configure it according to your needs.

    Issue the following commands:

    vzctl create <CT_ID> --pkgset name [options]

    vzctl set <CT_ID> <setting_name> <value> [--save]


    • <CT_ID> defines an arbitrary container ID number higher than 100, which is unique on the hardware node
    • --pkgset name denotes the operating system template to be used for Container creation
    • --save switch tells vzctl whether to save changes into the Container configuration file

      Note: For details on the Container creation and configuration options, refer to the Virtuozzo containers for Windows Reference Guide located at the Virtuozzo website.

    The commands below do the following:

    • Create a Container with ID 444 and IP, based on the OS template w2k3.
    • Set a disk space limit to 4+ gigabytes, private memory limit to 1 gigabyte and Administrator's password to "P4$$w0rd".
    • Enable Power Panel on the vzpp port with the "--offline_management yes --offline_service vzpp" options.

      Important: It is mandatory to use exactly these values for the options to ensure the Plesk compatibility with the Virtuozzo environment.


Important: Plesk needs the container to be configured with an IPv4 address in order to work properly.

vzctl create 444 --pkgset w2k3 --ipadd

vzctl set 444 --save --diskspace 4500000 --vprvmem 1024 --userpasswd Administrator:P4$$w0rd

vzctl set 444 --save --offline_management yes --offline_service vzpp

  1. Start the newly created Container:

    vzctl start <CT_ID>

  2. Install the Microsoft .NET framework version 2.0 or later into your Container:

    vzpkgadd <CT_ID> <dotnet_template_name>

    For example,

    vzpkgadd 444 dotnet2.0_frmwk-2.0.50727.42/20070613

  3. Install the Plesk template into the Container:

    vzpkgadd <CT_ID> <plesk_template_name>

    For example,

    vzpkgadd 444 PANEL_10.0.0/20100804.10

To clone a Container:

Issue a command in the following format:

vzmlocal -C <em><CT_List></em>
<em><CT_List></em> = <em><source_CTID></em>:<em><dest_CTID></em>[:<em><dest_private></em>] [options]

You should specify the source Container ID (<source_CTID>) and the destination Container ID (<dest_CTID>). Specifying the destination Container private area path (<dest_private>) is optional; it allows you to override the default path of X:\vz\private\<CT_ID>. For details on the command options, refer to the Virtuozzo Containers for Windows Reference Guide located at the Virtuozzo website.

For example, to clone the Container with Plesk created during the previous procedure, issue the following command:

vzmlocal -C 444:445