Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

LXD review

A broad Linux systems manager for teams that need containers, VMs, and infrastructure control.

8.8/10Editor score
LXD8.8 Visit LXD

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

LXD is an open-source manager for full Linux systems running as system containers or virtual machines. Maintained within the Canonical family, it is aimed at developers, infrastructure teams, and organizations managing workloads from individual workstations through production data centers. Its management surface includes a command-line client, web interface, and REST API, while its free and open-source model suits teams that want control over deployment and infrastructure without a paid product tier.

Its strongest fit is breadth of systems management. LXD can create instances from images, organize them with projects and profiles, configure storage and networking, and apply limits to CPU, memory, network I/O, disk space, and kernel resources. Snapshots support scheduling and automatic expiry, while live migration and stateful snapshotting help with workload movement. Clustering extends management across containers and virtual machines, and hardware passthrough covers GPUs, USB devices, NICs, disks, and other hardware. Custom image building is available through LXD image builder.

LXD also fits environments that need an API-led ecosystem. Its REST API manages instances, networks, storage, and other resources, and integrations include Kubernetes CSI, MAAS, and MicroCloud. The platform supports Linux containers and Linux virtual machines across a Linux host, while Windows is supported for virtual machines rather than Windows containers. Teams should choose LXD when they need a unified control layer for system containers and VMs, with infrastructure organization and migration built in. It is less suitable for workflows centered specifically on Windows containers or image formats explicitly documented as OCI or Docker.

LXD pros and cons

  • Where it wins
    • Manages system containers and virtual machines through one interface
    • Combines clustering, migration, snapshots, and detailed resource limits
    • Offers REST, web, CLI, image building, and hardware passthrough
  • Where it doesn't
    • Requires a Linux host operating system
    • Does not provide Windows containers
    • Uses its own image format rather than explicitly OCI or Docker

LXD fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update