New-PveNodesLxcClone

Create a container clone/copy

API: POST /nodes/{node}/lxc/{vmid}/clone, Proxmox VE API viewer

Aliases: Copy-PveLxc

Syntax

New-PveNodesLxcClone
    [-PveTicket <PveTicket>]
    [-Bwlimit <float>]
    [-Description <string>]
    [-Full <bool>]
    [-Hostname <string>]
    -Newid <int>
    -Node <string>
    [-Pool <string>]
    [-Snapname <string>]
    [-Storage <string>]
    [-Target <string>]
    -Vmid <int>
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Bwlimit	float	No	Override I/O bandwidth limit (in KiB/s).
-Description	string	No	Description for the new CT.
-Full	bool	No	Create a full copy of all disks. This is always done when you clone a normal CT. For CT templates, we try to create a linked clone by default.
-Hostname	string	No	Set a hostname for the new CT.
-Newid	int	Yes	VMID for the clone.
-Node	string	Yes	The cluster node name.
-Pool	string	No	Add the new CT to the specified pool.
-Snapname	string	No	The name of the snapshot.
-Storage	string	No	Target storage for full clone.
-Target	string	No	Target node. Only allowed if the original VM is on shared storage.
-Vmid	int	Yes	The (unique) ID of the VM.

Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.

Output

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.