I discovered Incus and IncusOS recently, and they seem like a very cool foundation for a self-hosted setup.

I’m thinking of using them with incus-compose to declare my setup.

Does anybody use them? I’d love to get some feedback. Are they stable and polished yet, or are there still a lot of sharp edges?

They mention “designed for modern systems” on their website. Are there any issues running it on a roughly 10-year-old laptop?

  • Denys Nykula@piefed.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 hours ago

    Is incus-compose a part of the base system, or an add-on? How does it work on IncusOS if it’s a command-line tool and there’s neither a remote nor a local shell, only a web API? Does it provide a built-in way to automate container updates?

    • moonpiedumplings@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 hours ago

      Is incus-compose a part of the base system, or an add-on

      it’s a program you install on your client machine. It just connects to the Incus API (probably using the Incus cli).

      How does it work on IncusOS if it’s a command-line tool and there’s neither a remote nor a local shell, only a web API?

      The Incus cli connects to the API.

      Does it provide a built-in way to automate container updates

      For the most part, Incus containers are system containers, similar to lightweight virtual machines. They run a full distro, including systemd and all that. For keeping those updating, you would want to use the auto update methods that Linux distros provide.

      There are also OCI containers that Incus can run, but I don’t think there is any form of auto update for those. You might be better off just running docker/podman/kubes in a VM for that.