With this command, you can create regular Containers. A unique Container ID is required for this command.
Name
|
Description
|
<CT_ID>
|
ID to assign to the new Container.
|
--vmtype ct
|
Tells the
prlctl create
command to make a Container. If the option is omitted, a virtual machine is created instead.
|
--ostemplate
<name>
|
OS EZ template to use for creating the Container. If omitted, this value is taken from the
DEF_OSTEMPLATE
parameter in the global Parallels Cloud Server configuration file.
|
--config
<name>
|
Container sample configuration file to use for creating the Container. Sample configuration files are located in
/etc/vz/conf
and have names in the format
ve-<
name
>.conf-sample
. The sample configuration files usually have a number of resource control limits for the Container and some application templates to be added to the Container immediately upon its creation. If you skip this option and the default configuration file name is not specified in the global Parallels Cloud Server configuration file, you will have to set resource control parameters for the Container using the
prlctl set
command.
|
--uuid
<uuid>
|
A custom UUID to assign to the Container.
|
--private
<path>
|
Path to the Container private area. This option is used to override default path to private area from the
/etc/vz/vz.conf
configuration file (
VE_PRIVATE
variable). The argument can contain
$VEID
string which will be replaced by numeric Container ID value.
Note:
Currently, this option may not be supported by the
prlctl
utility. Use
vzctl
instead.
|
--root
<path>
|
Path to the mount point of the Container root directory. This option is used to override default path to Container root directory from the
/etc/vz/vz.conf
configuration file (
VE_ROOT
variable). The argument can contain
$VEID
string which will be replaced by numeric Container ID value.
Note:
Currently, this option may not be supported by the
prlctl
utility. Use
vzctl
instead.
|
--ipadd
<addr>
[
/
mask
]
|
IP address and subnet mask to assign to the Container. If you omit this option, you can set an IP address for the Container later using the
prlctl set
command.
Note:
Currently, this option may not be supported by the
prlctl
utility. Use
vzctl
instead.
|
--hostname
<name>
|
Hostname to assign to the Container. If you omit this option, you can assign a hostname to the Container later using the
prlctl set
command.
Note:
Currently, this option may not be supported by the
prlctl
utility. Use
vzctl
instead.
|
--description
<desc>
|
Custom Container description.
Descriptions with white spaces must be enclosed in quotation marks.
Note:
Currently, this option may not be supported by the
prlctl
utility. Use
vzctl
instead.
|
--skip_app_templates
|
Do not install the application templates specified in the Container sample configuration file.
Note:
Currently, this option may not be supported by the
prlctl
utility. Use
vzctl
instead.
|
--velayout
<velayout_ID>
|
Defines the Container layout.
velayout_ID
can be one of the following:
-
5
: create a Container with the new Container-in-a-file layout. The new layout has been redesigned to store all files of a Container in a single image, similar to a virtual machine's hard disk.
This is the default and recommended layout in Parallels Cloud Server 6.0.
-
4
: create a Container based on VZFS, the obsolete layout used in earlier versions of Parallels Server Bare Metal.
If you omit this option, the layout will be defined by the
VEFSTYPE
parameter in the global configuration file
/etc/vz/vz.conf
. For the Container-in-an-image layout, this parameter should be set to
ext4
.
|