So I saw a blog post linked on here the other week about someone's homelab where they use #Incus to run all their containers and VMs. And I've fallen into the rabbit hole.

That post: https://linderud.dev/blog/personal-infrastructure-setup-2026/

Anyway, Incus is the fork/successor to #LXD which as recently as last year they released #IncusOS which is a very slimmed down OS for running multiple types of containers and VMs. A bit like #Proxmox in a sense.

What I like about the distro:
- Immutable
- A-side/B-side partition layout for friendlier updates
- Requires Secure Boot + TPM, resulting in encrypted drives by default
- ZFS. I've loved ZFS for many years.

It really seems like this was built for edge type deployments where secure "appliance" like things really excel yet still a net benefit elsewhere.

Since vSphere was killed, this feels pretty damn close to what I liked about it.

Can already run VMs along side "System Containers" (shared kernel + init system) and "App Containers" (what everyone calls "Docker"). I see on the roadmap support for MicroVMs (OCI container + individual kernel).

I run all of my stuff bar storage on #k3s on baremetal but there's times when I need a VM or different container behaviour than it offers.

"LXD: The Uprising Begins"
Ich dachte wir wären alle zu Incus gewechselt…

#LXC #LXD #Linux #Incus #Netflix

I think a lot of the cloud providers get lost in well... the cloud. 😅

You can do what #flyio #sprites does with #lxd/#incus system containers. It has all the ec2 magic there as well.

App containers help packaging software. But inhibit developing the software itself.

https://fly.io/blog/code-and-let-live/

A little #LXD helper I made recently

https://github.com/DanielDewberry/lxc-summary

I tried using #Incus because that problem related to #LXD, but now I'm using LXD for a couple reasons, like I can get a fresh version of LXD over snap, which I can't do with Incus, so I need to use the LTS version available on Ubuntu, the network in the container just works with LXD, and Incus I can't get network in the container, just in the VM, and I can get daily versions from Ubuntu with LXD but not with Incus.

Really useful video about networking options to access services running in LXD or Incus instances by @stgraber
https://www.youtube.com/watch?v=TmGvbXfwJEA

#incus #lxd #networking #linux #linuxcontainer #vm #virtualmachine

https://danieldewberry.com/blog/2025-12-05-ssh-into-a-lxd-instance/

SSH into a LXD instance

#ubuntu #lxd

LXD 6.6, il gestore di container e VM di Canonical, introduce i placement groups, il driver CSI per Kubernetes e il supporto storage HPE Alletra per ambienti enterprise. #Linux #Canonical #LXD

https://www.linuxeasy.org/lxd-6-6-rilasciato-placement-groups-csi-driver-kubernetes-e-supporto-hpe-alletra/?utm_source=mastodon&utm_medium=jetpack_social

LXD 6.6 container & virtual machine manager introduces placement groups, a Kubernetes CSI driver, improved volume recovery, and support for new HPE Alletra storage.
https://linuxiac.com/lxd-6-6-container-virtual-machine-manager-released/

#opensource #containerization #lxd #canonical

LXD-Fork erhält mit IncusOS seine eigene Distribution
https://linuxnews.de/lxd-fork-erhaelt-mit-incusos-seine-eigene-distribution/ #lxd #incus #incusos #linux #linuxnews

Neat output to show you the #lxd lxc containers used for #snapcraft :

alias snapcraft_lxc='lxc list --project snapcraft --columns nstS --format compact'

#DWDsTips

Problem: 100+ containers. No idea what did what. Docs scattered. SSH warnings. Name collisions.
I built LabKit to stop drowning in Incus containers.
A lightweight CLI to manage dev labs with:
- Git-tracked structure
- Auto-docs per node
- `lab up/down` with deps
- Scoped names (no more collisions)
- `--dry-run` everywhere
- Bidirectional deps

Now every lab knows its purpose.

GitHub: https://github.com/aprksy/labkit

#incus #lxd #linux #devops #cli #opensource #homelab

Preparing an #LXD to #Incus migration and just discovered I made a 5TB LV last year... then never gave it to LXD.
Someone just discovered 5TB of easy storage for his migration!

Another highlight from the #Ubuntu booth at #IndiaFOSS2025 ✨

An attendee tried out Magic (Open Sourve VLSI layout tool) — running smoothly inside an #Ubuntu 25.10 VM created with LXD ⚡

Needless to say, LXD was buzzing at the booth! 🚀

#OpenSource #Linux #LXD #VLSI #FOSS

The #Ubuntu 🇮🇳 booth at #IndiaFOSS2025 was full of energy today!

Attendees explored snaps, LXD, and more — but the real wow moment was a nested VM setup:
👉 An Arch container running inside an #Ubuntu 25.10 LXD VM 🤯

#OpenSource #Linux #LXD #FOSS

for anyone like me who is very very (very) late to the Linux #LXC party, this explains why #LXD has been replaced with #Incus.

tl;dr: #Canonical ruined things with a embrace-extend-extinguish play of relicensing and requiring contributors to sign a CLA to contribute to LXD.

https://discuss.linuxcontainers.org/t/lxd-has-been-re-licensed-and-is-now-under-a-cla/18454

LXD 6.5 is out now, bringing PCI hotplug, OIDC secret support, QEMU 9.1 compatibility, dark mode UI, and better VM directory disk hotplugging.
https://linuxiac.com/lxd-6-5-container-virtual-machine-manager-released/

#lxd #virtualization #containerization #opensource

My head hurts. Doing a deep-dive into containerization/VM with #Jenkins. So many options. I think I'll give #LXD a shot. But frankly, since my #OpenMPI program is already containerized via #Apptainer, I'll just go ahead and build on the (fairly powerful) Jenkins host for now, just to get the pipeline built as a proof of concept.

Time for an adult beverage.