X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pct.adoc;h=2cb4bbe8c4eacf0da871ef030ecce624a672415a;hp=12b9765358c7026ab920b33672004c8f876e6f51;hb=a45c999b4586734621bbc968d67f87390739b270;hpb=304eb5a9e1f05427c8c87121e75e0b305c411be8 diff --git a/pct.adoc b/pct.adoc index 12b9765..2cb4bbe 100644 --- a/pct.adoc +++ b/pct.adoc @@ -83,7 +83,7 @@ Technology Overview * CRIU: for live migration (planned) -* Use latest available kernels (4.4.X) +* Runs on modern Linux kernels * Image based deployment (templates) @@ -143,7 +143,7 @@ and will not be moved. Modification of a file can be prevented by adding a `.pve-ignore.` file for it. For instance, if the file `/etc/.pve-ignore.hosts` exists then the `/etc/hosts` file will not be touched. This can be a -simple empty file creatd via: +simple empty file created via: # touch /etc/.pve-ignore.hosts @@ -320,6 +320,26 @@ ACLs allow you to set more detailed file ownership than the traditional user/ group/others model. +Backup of Containers mount points +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +By default additional mount points besides the Root Disk mount point are not +included in backups. You can reverse this default behavior by setting the +*Backup* option on a mount point. +// see PVE::VZDump::LXC::prepare() + +Replication of Containers mount points +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +By default additional mount points are replicated when the Root Disk +is replicated. If you want the {pve} storage replication mechanism to skip a + mount point when starting a replication job, you can set the +*Skip replication* option on that mount point. + +As of {pve} 5.0, replication requires a storage of type `zfspool`, so adding a + mount point to a different type of storage when the container has replication + configured requires to *Skip replication* for that mount point. + + [[pct_settings]] Container Settings ------------------ @@ -328,6 +348,8 @@ Container Settings General Settings ~~~~~~~~~~~~~~~~ +[thumbnail="screenshot/gui-create-ct-general.png"] + General settings of a container include * the *Node* : the physical server on which the container will run @@ -371,7 +393,7 @@ or greater than 220. CPU ~~~ -[thumbnail="gui-create-ct-cpu.png"] +[thumbnail="screenshot/gui-create-ct-cpu.png"] You can restrict the number of visible CPUs inside the container using the `cores` option. This is implemented using the Linux 'cpuset' @@ -416,7 +438,7 @@ prioritize some containers. Memory ~~~~~~ -[thumbnail="gui-create-ct-memory.png"] +[thumbnail="screenshot/gui-create-ct-memory.png"] Container memory is controlled using the cgroup memory controller. @@ -435,7 +457,7 @@ swap`). Mount Points ~~~~~~~~~~~~ -[thumbnail="gui-create-ct-root-disk.png"] +[thumbnail="screenshot/gui-create-ct-root-disk.png"] The root mount point is configured with the `rootfs` property, and you can configure up to 10 additional mount points. The corresponding options @@ -465,6 +487,13 @@ in three different flavors: - Directories: passing `size=0` triggers a special case where instead of a raw image a directory is created. +NOTE: The special option syntax `STORAGE_ID:SIZE_IN_GB` for storage backed +mount point volumes will automatically allocate a volume of the specified size +on the specified storage. E.g., calling +`pct set 100 -mp0 thin1:10,mp=/path/in/container` will allocate a 10GB volume +on the storage `thin1` and replace the volume ID place holder `10` with the +allocated volume ID. + Bind Mount Points ^^^^^^^^^^^^^^^^^ @@ -516,7 +545,7 @@ NOTE: The contents of device mount points are not backed up when using `vzdump`. Network ~~~~~~~ -[thumbnail="gui-create-ct-network.png"] +[thumbnail="screenshot/gui-create-ct-network.png"] You can configure up to 10 network interfaces for a single container. The corresponding options are called `net0` to `net9`, and @@ -538,7 +567,7 @@ the following command: .Start and Shutdown Order // use the screenshot from qemu - its the same -[thumbnail="gui-qemu-edit-start-order.png"] +[thumbnail="screenshot/gui-qemu-edit-start-order.png"] If you want to fine tune the boot order of your containers, you can use the following parameters : @@ -561,6 +590,16 @@ start after those where the parameter is set, and this parameter only makes sense between the machines running locally on a host, and not cluster-wide. +Hookscripts +~~~~~~~~~~~ + +You can add a hook script to CTs with the config property `hookscript`. + + pct set 100 -hookscript local:snippets/hookscript.pl + +It will be called during various phases of the guests lifetime. +For an example and documentation see the example script under +`/usr/share/pve-docs/examples/guest-example-hookscript.pl`. Backup and Restore ------------------ @@ -690,6 +729,26 @@ NOTE: If you have changed the container's configuration since the last start attempt with `pct start`, you need to run `pct start` at least once to also update the configuration used by `lxc-start`. +[[pct_migration]] +Migration +--------- + +If you have a cluster, you can migrate your Containers with + + pct migrate + +This works as long as your Container is offline. If it has local volumes or +mountpoints defined, the migration will copy the content over the network to +the target host if there is the same storage defined. + +If you want to migrate online Containers, the only way is to use +restart migration. This can be initiated with the -restart flag and the optional +-timeout parameter. + +A restart migration will shut down the Container and kill it after the specified +timeout (the default is 180 seconds). Then it will migrate the Container +like an offline migration and when finished, it starts the Container on the +target node. [[pct_configuration]] Configuration