6,534
edits
Changes
created
This article describes how to use container-in-a-file technology aka [[ploop]]
== Requirements ==
* OpenVZ kernel 042stab052.8 or later
* vzctl 3.1 or later
* ploop-lib 1.1 or later
== Making a CT on ploop ==
=== Global configuration ===
In global VZ configuration file [[Man/vz.conf.5|/etc/vz/vz.conf]], set
VE_LAYOUT=ploop
This means that all new containers you will create will have ploop layout by default.
You don't have to set this option if you don't want ploop to be default. Alternatively, you can:
* use <code>--layout</code> option of <code>vzctl create</code> command;
* convert existing container to ploop.
=== Creating a new CT ===
To create a new container on ploop, use:
vzctl create ''CTID'' [--layout ploop] [--diskspace ''nnn''G]
# You can omit <code>--layout</code> option if you have set <code>VE_LAYOUT=ploop</code> in {{Man|vz.conf|5}}
# You can specify initial file system size using <code>--diskspace</code> option (example: 10G for 10 gigabytes)
# If <code>--diskspace</code> is not specified, the size defaults to DISKSPACE limit value in sample CT config used
=== Converting an existing CT ===
vzctl convert ''CTID''
== Resizing a ploop image ==
Ploop image can be resized in both directions (i.e. either shrank or grown). Ploop also supports online/live resize so you don't have to stop a CT to do resize.
To resize a ploop CT image (either online or offline), use
vzctl set ''CTID'' --diskspace ''nnn''G --save
== Using disk quotas inside container ==
If you want to use standard Linux per-user and per-group disk quota inside a container, you have to enable it using
vzctl set ''CTID'' --quotaugidlimit 1000 --save
Note that enabling or disabling in-container disk quotas requires container restart.
== See also ==
* [[Ploop]]
* {{Man|vz.conf|5}}
* {{Man|vzctl|8}}
== Requirements ==
* OpenVZ kernel 042stab052.8 or later
* vzctl 3.1 or later
* ploop-lib 1.1 or later
== Making a CT on ploop ==
=== Global configuration ===
In global VZ configuration file [[Man/vz.conf.5|/etc/vz/vz.conf]], set
VE_LAYOUT=ploop
This means that all new containers you will create will have ploop layout by default.
You don't have to set this option if you don't want ploop to be default. Alternatively, you can:
* use <code>--layout</code> option of <code>vzctl create</code> command;
* convert existing container to ploop.
=== Creating a new CT ===
To create a new container on ploop, use:
vzctl create ''CTID'' [--layout ploop] [--diskspace ''nnn''G]
# You can omit <code>--layout</code> option if you have set <code>VE_LAYOUT=ploop</code> in {{Man|vz.conf|5}}
# You can specify initial file system size using <code>--diskspace</code> option (example: 10G for 10 gigabytes)
# If <code>--diskspace</code> is not specified, the size defaults to DISKSPACE limit value in sample CT config used
=== Converting an existing CT ===
vzctl convert ''CTID''
== Resizing a ploop image ==
Ploop image can be resized in both directions (i.e. either shrank or grown). Ploop also supports online/live resize so you don't have to stop a CT to do resize.
To resize a ploop CT image (either online or offline), use
vzctl set ''CTID'' --diskspace ''nnn''G --save
== Using disk quotas inside container ==
If you want to use standard Linux per-user and per-group disk quota inside a container, you have to enable it using
vzctl set ''CTID'' --quotaugidlimit 1000 --save
Note that enabling or disabling in-container disk quotas requires container restart.
== See also ==
* [[Ploop]]
* {{Man|vz.conf|5}}
* {{Man|vzctl|8}}
