Incus and LXConsole

  • Has anyone tried installing Incus on OMV7 yet?


    The reason I'm asking is that I'd like to try it, I like the look of LXConsole which looks easier to read for me than the OMV's KVM plugin.


    Plus I like that Incus is not Ubuntu controlled and it seems to be very actively developed.

    I also like that there are a number of Youtube channels making video's on using Incus from the CLI or LXConsole.


    I know that we have the KVM plugin, which I do have installed, but I don't find it the easiest thing to use, I realise that is a 'me' problem rather than the software.


    If no-one has tried it. Before I spin up a OMV VM and try installing Incus on it, does anyone have a list of problems they think I may have to overcome?

    OMV Version 8.latest | AMD Ryzen 5600G with 64GB | JBOD EXT4 & BRTFS

    Various Unifi router & switches | Only Linux laptops and PC's

    • Official Post

    Has anyone tried installing Incus on OMV7 yet?

    It is in Debian backports. I tried it a while back but the web interface felt a lot like cockpit and the command line didn't seem to have any advantages over virsh.


    I like the look of LXConsole which looks easier to read for me than the OMV's KVM plugin

    While I am curious why the kvm plugin is hard to "read" or exactly what makes lxconsole easier to read, lxconsole isn't confined to the constraints of the OMV web interface. lxconsole seems to have advantages when using a cluster. Otherwise, I just see a lot of unneeded info if you are using a single node.


    Plus I like that Incus is not Ubuntu controlled and it seems to be very actively developed.

    Canonical doesn't control lxc. They control lxd. Since the plugin isn't using lxd at all, I don't see how Ubuntu control is a problem.

    I also like that there are a number of Youtube channels making video's on using Incus from the CLI or LXConsole.

    The kvm plugin works with virsh, the plugin itself, cockpit, virt-manger, or any other tool that supports libvirt.

    but I don't find it the easiest thing to use, I realise that is a 'me' problem rather than the software.

    Why? I bounce from omv kmv plugin to virsh to virt-manger to VMware to proxmox all day long and don't have issues with any of them. I try to make the plugin easy to use from my experience with those systems. I'm curious where I went wrong or somehow came up a system that is unusable enough to make people use a completely new system.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • It is in Debian backports. I tried it a while back but the web interface felt a lot like cockpit and the command line didn't seem to have any advantages over virsh.


    I've not used virsh, but have used cockpit on baremetal, didn't find it to bad.


    Upto now, I've mainly concentrated on docker, which I do like, for it's ease of use. I see incus is starting to allow some docker things going forward.


    I've also seen Truenas is going to use Incus (doesn't mean I think what Truenas does, then so should OMV) for me OMV is a lot better than Truenas, as I don't use ZFS, and a lot cleaner looking, it also works with my little JBOD system.


    For me being a homelab person, I like to try new stuff out and thought if someone else has given Incus a go, then I could save myself some work, if it didn't work or needed a work around for it to function correctly.

    While I am curious why the kvm plugin is hard to "read" or exactly what makes lxconsole easier to read, lxconsole isn't confined to the constraints of the OMV web interface. lxconsole seems to have advantages when using a cluster. Otherwise, I just see a lot of unneeded info if you are using a single node.

    It's a me thing regarding the use of the plugin, I've not done loads of vm or lxc. The last lxc I did, I wanted to increase disk space, couldn't see how to do it, where I know you can from incus.


    Regarding lxconsole, it just looked to me, easier to navigate, plus of course there seems to be more tutorials for Incus and lxconsole than OMV, but I can generally get my round OMV.


    Canonical doesn't control lxc. They control lxd. Since the plugin isn't using lxd at all, I don't see how Ubuntu control is a problem.

    My bad, I was under the impression lxc was a newer or subset of lxd.

    The kvm plugin works with virsh, the plugin itself, cockpit, virt-manger, or any other tool that supports libvirt.

    Perhaps I'll spend some time looking at the above as well. Always nice to see whats out there.

    Why? I bounce from omv kmv plugin to virsh to virt-manger to VMware to proxmox all day long and don't have issues with any of them. I try to make the plugin easy to use from my experience with those systems. I'm curious where I went wrong or somehow came up a system that is unusable enough to make people use a completely new system.

    Like I said earlier, I'm a simple homelab person, who see's something and thinks I'll learn that, and give it a go, sometimes it clicks straight away, others not. If there is more than one way of doing something, then to me thats good.


    The plugin is excellent, the same as the docker plugin is as well, but I also like Dockge for docker as well, and would of liked to jump between the 2, but I can't, so I've stuck with your compose plugin because it does all I want and more, but if the plugin used 'compose.yml' for the compose file, I could use either, but I'm grateful that OMV has some brilliant tools and maintainers.


    I haven't written any code since I ran a BBS, so I get it, when someone couldn't always see the software as I saw it, especially as I used to hate writing documentation. Which is why I like forums and try and help where I can.


    Obviously, it doesn't look as though anyone is interested in Incus, so I'll spin up some OMV vms and see how it goes.

    OMV Version 8.latest | AMD Ryzen 5600G with 64GB | JBOD EXT4 & BRTFS

    Various Unifi router & switches | Only Linux laptops and PC's

  • The KVM plugin is a good fit for OMV which is first and foremost a NAS appliance. Incus is a different beast, a container/vm orchestrator (more akin to Proxmox et al.) with managed storage. It doesn't mean there is no interest in Incus, it's just I don't see how it's possible for Incus to run under OMV in anything other than a VM. Just have a look at the official incus docs re: storage and networking:


    About storage pools, volumes and buckets
    Incus stores its data in storage pools, divided into storage volumes of different content types (like images or instances). You could think of a storage pool…
    linuxcontainers.org

    Networking
    About networking, Create and configure a network, Configure a network, Configure network ACLs, Configure network forwards, Configure network integrations,…
    linuxcontainers.org


    The fact that a forthcoming version of TrueNAS SCALE is to incorporate Incus in some (butchered?) form is not necessarily an endorsement. It's just another twist in the long running SCALE saga which backed some wrong horses and pursued what ended up as blind allies.

    • Official Post

    The last lxc I did, I wanted to increase disk space, couldn't see how to do it

    With the kvm plugin, lxc is just files on a filesystem. The container technically has whatever freespace is available on the filesystem you put the container on. If you need more space, you would have to change the size of the underlying filesystem.

    but if the plugin used 'compose.yml' for the compose file, I could use either,

    Since I assume you might use other tools to edit the compose.yml, that would just mean the compose plugin would be out of date (sure, there is a sync button but that is a manual step) or the compose plugin would overwrite a change from the other tool. Just seems like a headache to me and the plugin would need a significant change for it to happen. It would also break existing backups.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • The KVM plugin is a good fit for OMV which is first and foremost a NAS appliance. Incus is a different beast, a container/vm orchestrator (more akin to Proxmox et al.) with managed storage. It doesn't mean there is no interest in Incus, it's just I don't see how it's possible for Incus to run under OMV in anything other than a VM. Just have a look at the official incus docs re: storage and networking:

    Fair enough. I've looked at Proxmox, but always come back to OMV, especially now I tend to use Docker containers.


    I don't really have a ton of use for VM's or LXC's, if I'm being honest with myself, not sure I want to spend the time updating them, but I may spin up the odd one going forward.


    The fact that a forthcoming version of TrueNAS SCALE is to incorporate Incus in some (butchered?) form is not necessarily an endorsement. It's just another twist in the long running SCALE saga which backed some wrong horses and pursued what ended up as blind allies.

    Scale is just more than I need, plus I don't use ZFS. I like the video's, but even when the Scale fans say how easy it is to use compared to Unraid or OMV, I'm not sure they've given OMV a good enough run, or really looked at the OMV extras properly.

    I'm not sure Scale has docker working correctly even now.

    OMV Version 8.latest | AMD Ryzen 5600G with 64GB | JBOD EXT4 & BRTFS

    Various Unifi router & switches | Only Linux laptops and PC's

  • Since I assume you might use other tools to edit the compose.yml, that would just mean the compose plugin would be out of date (sure, there is a sync button but that is a manual step) or the compose plugin would overwrite a change from the other tool. Just seems like a headache to me and the plugin would need a significant change for it to happen. It would also break existing backups.

    No, I get it, I came to accept it after I first asked you about it.


    It's all good :) I've cobbled a bash script that goes through the compose folder and copies OMV files to vanilla docker files for each folder.


    I don't see me changing from the plugin anytime soon, but the option is there, if I want to. Plus at the moment there are only a few programs that allow docker file manipulation.

    OMV Version 8.latest | AMD Ryzen 5600G with 64GB | JBOD EXT4 & BRTFS

    Various Unifi router & switches | Only Linux laptops and PC's

  • Hi,

    trythat any experience on this?


    My case:

    My first experience for server virtualization was LXD, than Incus on Ubuntu + Cockpit.

    Than I came to OMV and I liked. Now tried KVM plugin and also it looks good.

    My overall opinion is that I like OMV more.


    Now even thinking about completely migrate to OMV, but at the same time want to be sure what will be gains and what I will loose.

    So the question is for others too - do any body have experience with both KVM vs Incus ?

    • Official Post

    Now even thinking about completely migrate to OMV, but at the same time want to be sure what will be gains and what I will loose.

    So the question is for others too - do any body have experience with both KVM vs Incus ?

    Incus is LXC and KVM. The openmediavault-kvm plugin is LXC and KVM. They just use different web interfaces and the kvm plugin uses libvirt/virsh. Sure, there are things incus does that the kvm plugin does not do and vice versa. The biggest difference is probably the native cloud-init support in incus. Most OMV users don't need it though. It would be easier to give you a recommendation based on your use case.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    I need to manage some ~5max VMs, one or to of them Windows, the rest linux or mostly containers.

    Max 10 docker containers.

    I have up to 30 VMs including one win10 vm and one win11 vm with the kvm plugin. I usually have about 10 docker containers but many people have 50+ with the compose plugin. So, no problems there.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    How can I migrate Incus VMs and Containers to KVMs ?

    For the VMs, it would depend on how the underlying storage is setup. If you are using qcow2 files, it would be easy. Just create a new VM and attach the disks. If you using something, it would be trickier. You could always use something clonezilla to backup the VM and restore it to a new VM. Sounds like a lot of work for little gain. Might as well just stay with incus. I don't have a good suggestion for how to migrate containers.


    I am using them on my Incus servers.

    Optimal use is very subjective statement. Using zfs and btrfs does allow some different features but are they really more optimal than qcow2 files? I would say no. VMware doesn't use zfs and btrfs methods and sticks with vmdk files.


    Either way, I would stay where you are since the effort to move seems like moving would provide little to no benefit.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!