LXD uses QEMU/KVM/libvirt for VMs thus the performance is at least the same as any other QEMU solution like Proxmox, the real difference is that LXD has a much smaller footprint, doesn’t depend on 400+ daemons thus boots and runs management operations much faster. The virtualization tech is the same and the virtualization performance is the same.
Sorry I meant high availability as in the ability to live transfer a VM to a different host without downtime or service interruptions.
Oh, my bad then. But yes, like Proxmox, LXD/Incus can do live migrations of VMs since 4.20 (2021 I believe). Live migration of containers can be done under specific circunstantes as well.
Are you using a container runtime in the LXC container? (i.e. docker or podman)
In some of them yes. At least under Debian as long as you’ve set security.nesting=true it will work fine.
LXD uses QEMU/KVM/libvirt for VMs thus the performance is at least the same as any other QEMU solution like Proxmox, the real difference is that LXD has a much smaller footprint, doesn’t depend on 400+ daemons thus boots and runs management operations much faster. The virtualization tech is the same and the virtualization performance is the same.
Maybe I’m just doing it wrong. I’ve just found LXD to be lacking as you can’t live transfer it to a different host. It is also slower than Docker and Podman and I was unable to get docker running in a unprivileged LXC container. I think it should be possible to run docker in LXC but by the time I spend the effort is is more secure and easier to use a full virtual machine.
Maybe I should revisit the idea though as it seems like many people stand by it.
*proxmox*
oh, fuck. really? what if i have 12 year old copy?
I meant you should switch to proxmox. What are you referring to?
No this is Patrick.
Spongebob is that you?
He should really switch to LXD/Incus, not Proxmox as it will end like ESXi one day.
Lxd is slow and doesn’t support HA
LXD uses QEMU/KVM/libvirt for VMs thus the performance is at least the same as any other QEMU solution like Proxmox, the real difference is that LXD has a much smaller footprint, doesn’t depend on 400+ daemons thus boots and runs management operations much faster. The virtualization tech is the same and the virtualization performance is the same.
Here’s one of my older LXD nodes running HA:
It’s “so hard” to run HA under LXD… you just have to download the official HA OS image and import to LXD.
Sorry I meant high availability as in the ability to live transfer a VM to a different host without downtime or service interruptions.
I hear that I lot of people are using LXC. Are you using a container runtime in the LXC container? (i.e. docker or podman)
Oh, my bad then. But yes, like Proxmox, LXD/Incus can do live migrations of VMs since 4.20 (2021 I believe). Live migration of containers can be done under specific circunstantes as well.
In some of them yes. At least under Debian as long as you’ve set
security.nesting=trueit will work fine.*LXD/Incus*
LXD is not really usable for anything as it is very slow
LXD uses QEMU/KVM/libvirt for VMs thus the performance is at least the same as any other QEMU solution like Proxmox, the real difference is that LXD has a much smaller footprint, doesn’t depend on 400+ daemons thus boots and runs management operations much faster. The virtualization tech is the same and the virtualization performance is the same.
Maybe I’m just doing it wrong. I’ve just found LXD to be lacking as you can’t live transfer it to a different host. It is also slower than Docker and Podman and I was unable to get docker running in a unprivileged LXC container. I think it should be possible to run docker in LXC but by the time I spend the effort is is more secure and easier to use a full virtual machine.
Maybe I should revisit the idea though as it seems like many people stand by it.
It isn’t lacking… https://linuxcontainers.org/incus/docs/main/howto/move_instances/#move-instances but as with Proxmox there are details when it comes to containers. VMs can fully migrate live.
What host OS are you running on? Did you set
security.nesting trueon said container?I probably just set it up wrong.