• 0 Posts
  • 1.07K Comments
Joined 2 months ago
cake
Cake day: May 3rd, 2024

help-circle
  • Yeah, I think it’s an unusual case, but I wanted to bring it up to support your point about rejecting their kernel and distro. You can put Incus on a lot of different systems. Don’t like systemd? Put it on Void. Want a declarative setup? NixOS. Minimalist? Alpine.

    Do I want to maintain a full operating system just to run this one type of software? No, that’s absurd. I want to choose the distro I want to work with and then have the software work on top of it.


  • I think I was on a previous account the last time I saw you, glad to see you’re still posting. You convinced me to move from Proxmox to Incus a while back. Sure, I had some growing pains, but it’s pretty smooth now.

    I like that I can switch out my distros underneath Incus instead of being stuck on one weird kernel. IME you were absolutely right about that. I’m getting into atomic distros to manage homelab machines. I would not be able to do that on Proxmox.

    I also don’t need to edit a giant Javascript file to remove a nag about enterprise software repos, which is nice.










  • The problem I’m running into is attempting to create an image fresh from the yaml “treefile” and building on that. I think I know what they’re using but the documentation on how to reproduce the build isn’t great.

    I’d also like to isolate the build into containers, which makes the whole thing harder because the build process uses containers and loop devices.

    You might get up and running faster if you start from an existing atomic distro and layer packages on top. The ublue-os repos have an automated script that you could use as a reference.






  • Hell yeah! I’m on Bazzite, myself. I’m ok with KDE but might swap it out later. Did you rebase to get from Bazzite to Sway?

    I think the ostree stuff is really neat. Nix sounds like a great complement to it, I guess you can configure it to install to /var pretty easily? I think I’d prefer that to brew.

    I’ve been interested in ostree so much that I’m moving a few other things over to IoT. Building your own makes too much sense, updating layers is so slow. I’m trying to use rpm-ostree compose to make my own version of IoT but I am struggling to modify the containers it builds or turn them into ISOs. All of their tooling is needlessly complex.