• Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    1
    ·
    5 months ago

    That actually could be really handy. I’ll have to check it out once this release moves downstream.

    • TCB13@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      5 months ago

      Yeah, meanwhile I’ll keep using LXD / Incus for both containers and VMs.

      Incus has a few advantages: an image repository, a nicer container manager (cli tools) and sane security defaults. By default Incus assumes your containers should be isolated and secure environments while systemd-nspawn is more about quick and dirty containers useful to compile something or run some trusted task.

      • llii@discuss.tchncs.de
        link
        fedilink
        arrow-up
        5
        ·
        5 months ago

        The thing with Incus is that you get the image repository and manager and the permissions applied to containers make them isolated and secure environments by default running on another user etc etc

        This is really hard to read.