When deploying system containers using Incus (v6.0 LTS) or LXD (v5.21 LTS) on cloud virtual private servers (such as VPSTTT VPS instances), underlying infrastructure architecture plays a critical role in performance and reliability.
Environment Context
- Host OS: Ubuntu 24.04 LTS on VPS host
- Container Runtimes: Incus 6.0 / LXD 5.21 LTS
- Storage Driver: ZFS or Btrfs backends
- Networking: Managed bridge (
incusbr0/lxdbr0) with routed IPv4/IPv6
Technical Infrastructure Overview
Running container hypervisors on KVM-based VPS instances requires evaluating storage driver performance (e.g., ZFS dataset options vs. Btrfs subvolumes) and network interface bridging. When raw block storage is allocated to the VPS host, ZFS pools offer snapshot efficiency but require proper memory tuning for the ARC cache.
Diagnostic Setup
To evaluate network bridge parameters and storage performance on your VPS host, run standard diagnostic commands:
# Verify container storage pool health
incus storage list
incus storage info default
# Check network interface routing
incus network show incusbr0
What are the community best practices for tuning ZFS ARC limits and block storage I/O when running high-density Incus/LXD containers on virtual private server environments?
#incustech LXD #vps #containers #infrastructure