hellostick@lemm.ee to Linux@lemmy.ml · 3 days agoVirt-Manager, use deb version of flatpak version??message-squaremessage-square17fedilinkarrow-up137arrow-down13
arrow-up134arrow-down1message-squareVirt-Manager, use deb version of flatpak version??hellostick@lemm.ee to Linux@lemmy.ml · 3 days agomessage-square17fedilink
minus-squareliliumstar@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up20·3 days agoI would use the native version. For something like this, it makes sense that it should have less restricted/sandboxed access to the underlying system.
minus-squarehellostick@lemm.eeOPlinkfedilinkarrow-up2·2 days agoi am not sure which one is the native version… you mean the version packaged by the distro (deb) or the developer (flatpak)?
minus-squareliliumstar@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up2·2 days agoIn this case I meant the one packaged by your distro.
minus-squarealteredEnvoy@sopuli.xyzlinkfedilinkarrow-up14·3 days agoHmm, wouldn’t the virt manager just be a frontend and communicate with the virtd socket though?
minus-squaredeadcade@lemmy.deadca.delinkfedilinkarrow-up8arrow-down1·3 days agovirt-manager only requires access to the libvirtd socket, as long as the flatpak.has that as default configuration (which I imagine would be the case), there’s zero difference beteween flatpak and native.
minus-squaredeafboy@lemmy.worldlinkfedilinkarrow-up1·2 days agoIn my experience, this is not the case. It just says it can’t connect. Doesn’t specify how or where to.
minus-squarehellostick@lemm.eeOPlinkfedilinkarrow-up1·2 days agoactually there is difference in version between the two. deb by my distro is in 4.0.0 (mar, 2022) while flatpak is 5.0.0 (nov, 2024)
I would use the native version. For something like this, it makes sense that it should have less restricted/sandboxed access to the underlying system.
i am not sure which one is the native version… you mean the version packaged by the distro (deb) or the developer (flatpak)?
In this case I meant the one packaged by your distro.
Hmm, wouldn’t the virt manager just be a frontend and communicate with the virtd socket though?
virt-manager only requires access to the libvirtd socket, as long as the flatpak.has that as default configuration (which I imagine would be the case), there’s zero difference beteween flatpak and native.
In my experience, this is not the case. It just says it can’t connect. Doesn’t specify how or where to.
actually there is difference in version between the two. deb by my distro is in 4.0.0 (mar, 2022) while flatpak is 5.0.0 (nov, 2024)