LXC Virtualization

WARNING

If you plan to run more than 200 LXC containers on one server, this solution is not recommended. lxcfs drift can cause persistent I/O load that is hard to recover from. (This is an upstream LXC limitation.)

Images available for creating LXC Containers

x86_64:

Auto-patching images: https://github.com/oneclickvirt/lxc_amd64_images/blob/main/all_images.txt

TIP

Automated daily pulls for compilation and patching

Self-patching images: https://github.com/oneclickvirt/pve_lxc_images/blob/main/fixed_images.txt

TIP

Some of these images are flawed and not guaranteed to be available for all PVEs, with names like ubuntu16.04, debian6, centos7, opensuse42.2, opensuse42.3 Don't use them unless necessary.

and

Run pveam available --section system to see the names and version numbers of the officially available systems.

Priority: Self-patching images (not supported by Proxmox-VE 5 and below) > Official default images (both supported) image

The version has been automatically recognized by a script to use the corresponding image.

arm:

https://github.com/oneclickvirt/lxc_arm_images/blob/main/all_images.txt

Supported systems can be viewed in the file above, which lists debian and ubuntu systems do not use the aliases in it, just use the numeric designators.

An ARM64 PVE template for openEuler 24.03 is also available in the maintained release. Select a filename starting with openeuler_24.03_24.03_arm64_default_ and ending with _arm64.tar.zst for a native ARM64 host. The existing provisioning scripts continue to use the LXC image list above.

The central CNB build repository checks for updates weekly and also supports manual builds. The source and recompressed template are checked for executable architecture and inherited SSH host identities, then tested for container boot, the SSH listener, HTTPS/DNS and restart in an isolated ARM64 environment. Only passing templates are uploaded to GitHub Releases; CNB object storage is not used. Basic container runtime checks use Incus. Creation with pct and network setup on PVE/PXVIRT still need verification on the actual host.

TIP

All system parameters are lowercase system names spliced with version numbers, e.g. debian11, ubuntu22, etc. (Self-patched images support some out-of-the-way systems, such as centos6, centos7, debian8, debian9, etc.)

The default CT username for all systems is root

TIP

Of course, sometimes there are special cases where the version may be current/base, in which case it is sufficient to use only the English system name, e.g. archlinux, gentoo, kali.

Creating Individual LXC Containers for Virtualization

WARNING

Before initial use, ensure that the current PVE (Proxmox Virtual Environment) is clean and the host machine has not undergone any port mapping, as conflicts in settings could lead to bugs.

TIP

Before creating containers, use the 'screen' command to run them in the background. This helps to avoid extended creation times that might lead to interruptions due to unstable SSH connections.

• Automatically create NAT servers using the default Debian 11 image, or customize the system image as needed.
• Automatically perform internal and external network port mapping, including ports 22, 80, 443, and 26 additional ports with identical numbers for both internal and external networks.
• After generation, allow some time for the virtual machine to configure its internal network and login information. This process takes approximately 3 minutes.
• The default network configuration includes port mappings for 22, 80, 443, and a range of 26 ports for both internal and external networks.
• Customize the number of cores, memory size, disk size, and the storage disk on the host machine for allocation. Ensure that you calculate available resources before creating containers.
• Optionally specify the storage disk location in the command. When not specified, it defaults to the local disk, which is the system disk. Alternatively, you can specify a mount disk as displayed in PVE.
• The created containers are enabled with SSH by default, allowing root login. They are also configured to support nested virtualization for Docker.
• Relevant container information will be stored in the respective container's notes, accessible through the web interface.
• If the host machine has an IPv6 subnet, IPv6 networking will be automatically attached, but no public IPv6 addresses will be provided.
• Standalone IPv6 is optional. The upstream network must allow additional public addresses, and the corresponding gateway must be configured as described in installation.

Usage Instructions

Download Script

curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct.sh -o buildct.sh && chmod +x buildct.sh

Meaning of each parameter

# ./buildct.sh CTID Password Number_of_CPU_Cores Memory Disk SSH_Port Port_80 Port_443 Start_Public_Port End_Public_Port System Storage_Disk Independent_IPV6_address(leave default N blank)

Memory is in MB and disk size is in GB. An optional 14th argument accepts a public IPv4/CIDR or auto; PVE_CT_PUBLIC_IPV4 can also set it. Leave it empty to keep the NAT workflow above.

When set, the container receives the public IPv4 directly on vmbr0 and uses SSH port 22, without IPv4 port mappings. auto selects a free address in the host subnet. A manually supplied address must include its prefix length, be assigned by your provider and be unused. For example:

./buildct.sh 111 oneclick123 1 512 5 0 0 0 0 0 debian11 local N 203.0.113.10/24

The public address is an example; replace it with your own.

Test Example

./buildct.sh 111 oneclick123 1 512 5 20001 20002 20003 30000 30025 debian11 local N

After setting up, you can execute cat ct111 to view the information, or check the NOTES section on the web interface.

Here is the information for the created example CT:

Attribute	Value
CTID	111
SSH Username	root
SSH Password	oneclick123
Number of CPU Cores	1
Memory Size	512MB
Disk Size	5G
SSH Port	20001
Port 80	20002
Port 443	20003
Port Range for NAT	30000 to 30025
Operating System	debian11
Host Storage Disk	local
IPv6 address	N

TIP

Note that only CTIDs from 100 to 256 can be used here, no other numbers can be used. The NAT script above additionally requires an ID no higher than 254 to form a usable IPv4 address.

Create without inbound port mappings

Set all five SSH, HTTP, HTTPS, first-range-port and last-range-port arguments to 0. This retains the private address and outbound access without creating inbound mappings. Connect to SSH port 22 from the host or a reachable private network. For example, after downloading the script above:

./buildct.sh 111 MyPassword 1 512 5 0 0 0 0 0 debian11 local N

A failure to write requested port mappings returns an error instead of reporting an unreachable instance as successful.

Deletion specific CT

• Stop CT
• Delete CT
• Delete Port Mapping
• Restart ndpresponder if the service is in use
• Delete Log Files

Download Script

curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/pve_delete.sh -o pve_delete.sh && chmod +x pve_delete.sh

Meaning of each parameter

You can delete the CT with the corresponding CTID, as demonstrated here using the example 111 above

./pve_delete.sh 111

The actual number of deletions is not fixed, a space separates each CTID, and more than one can be deleted at a time.

Batch Creation of LXC Containers with NAT

WARNING

Make sure the current Proxmox Virtual Environment (PVE) is clean and the host machine has not undergone any port mapping before the first use, as conflicting settings may result in bugs.

TIP

Before initiating the creation process, it's recommended to use the 'screen' command to execute the batch creation. This will prevent interruptions due to potential instability in SSH during the extended creation time.

• It is possible to run the batch container creation process multiple times. However, please be mindful of allocating enough memory to the host machine to prevent system crashes. For adding swap space, refer to this link.
• There is a 60-second interval between creating each container to avoid sudden performance bottlenecks.
• Customization options include selecting the number of CPU cores, memory size, disk size, and the storage drive on the host machine. Ensure that you have calculated available resources appropriately before initiating the process.
• The created containers have SSH enabled by default, allowing root login. Additionally, they are configured to support nested virtualization for Docker usage.
• Relevant information about the containers will be stored in the corresponding container's notes, which can be viewed on the web interface.
• If the host machine has an IPv6 subnet, it will be automatically assigned to the containers. However, public IPv6 addresses will not be provided.
• Standalone IPv6 is optional. The upstream network must allow additional public addresses, and the corresponding gateway must be configured as described in installation.

Usage Instructions

Download Script

curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/create_ct.sh -o create_ct.sh && chmod +x create_ct.sh && bash create_ct.sh

After the setup is complete, you can execute cat ctlog to view the information, or check in the NOTES section on the web interface.

Delete All CT

• Delete all CTs
• Remove the corresponding port mappings and connection records
• Restart ndpresponder if the service is in use

Download pve_delete.sh as shown above, then run:

for id in $(pct list | awk 'NR>1{print $1}'); do
  ./pve_delete.sh "$id" || break
done

Creating Virtual Machines with Pure IPv6 Addresses

The premise is that the host provides an IPv6 subnet rather than a standalone IPv6 address, and the host does not have MAC address filtering enabled.

Automatic Selection of IPv6 Addresses, No Manual Configuration Needed

• Only IPv6 networking is configured, without an IPv4 address or inbound IPv4 ports. A usable public prefix provides public IPv6; otherwise, the current gateway configuration falls back to NAT66 outbound access
• Automatically detect available IPv6 ranges and bind the corresponding V6 address based on the container number to the container.
• Relevant system information will be stored in the NOTES of the corresponding container, accessible for viewing on the web interface.

Download script

Command:

curl -L https://raw.githubusercontent.com/oneclickvirt/pve/main/scripts/buildct_onlyv6.sh -o buildct_onlyv6.sh && chmod +x buildct_onlyv6.sh

Example Usage

./buildct_onlyv6.sh CTID Password Number_of_CPU_Cores Memory_Size_in_MB Disk_Size_in_GB Operating_System Storage_Disk

./buildct_onlyv6.sh 152 oneclick123 1 1024 10 debian13 local

The above command signifies the creation of a container with a pure IPv6 address.

Attribute	Value
Container Type	CT
CTID	152
Username	root
Password	oneclick123
CPU Cores	1
Memory	1024MB
Disk	10G
Operating System	debian13
Storage Disk	Local Disk (System Disk)

TIP

Note that only CTIDs from 100 to 256 can be used here, no other numbers can be used.