clicd-virtualization-panel

Use the CLI command clicd container create with flags for name, template, CPU, memory, disk, and network type, or send a POST request to /api/v1/containers with a CreateContainerRequest JSON body. The container can then be started with clicd container start or the start API endpoint.

Add a mapping with clicd nat add specifying the container, protocol, public port, and private port, or POST to /api/v1/nat. Ensure net.ipv4.ip_forward is enabled in sysctl and verify rules with iptables -t nat -L.

Yes, CLICD supports IPv6 with automatic prefix detection or a manually configured prefix in config.yaml. Enable net.ipv6.conf.all.forwarding and assign addresses via clicd ipv6 assign or the container IPv6 API endpoint.

The most common cause is disabled IP forwarding; enable it with sysctl -w net.ipv4.ip_forward=1 and persist it in /etc/sysctl.conf. Also verify the public IP in the CLICD config and check existing iptables NAT rules for conflicts.

Yes, POST to /api/v1/containers/batch-create with a count, name prefix, template, and resource specs to provision multiple containers at once. Batch start, stop, restart, and delete actions are available via /api/v1/containers/batch.

CLICD requires a Linux system with systemd, LXC or KVM/QEMU installed, root or sudo access, and iptables with conntrack-tools. Installation uses a one-click curl script that sets up a systemd service on port 8080 by default.