▲ 30 ▼ Virt-Manager, use deb version of flatpak version?? (lemm.ee) submitted 2 years ago by hellostick@lemm.ee to c/linux@lemmy.ml 16 comments fedilink hide all child comments
[–] liliumstar@lemmy.dbzer0.com 20 points 2 years ago (3 children) 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. permalink fedilink source hideshow 6 child comments replies: [–] alteredEnvoy@sopuli.xyz 15 points 2 years ago Hmm, wouldn't the virt manager just be a frontend and communicate with the virtd socket though? permalink fedilink source parent [–] deadcade@lemmy.deadca.de 8 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] hellostick@lemm.ee [S] 1 point 2 years ago 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) permalink fedilink source parent [–] deafboy@lemmy.world 1 point 2 years ago In my experience, this is not the case. It just says it can't connect. Doesn't specify how or where to. permalink fedilink source parent [–] hellostick@lemm.ee [S] 1 point 2 years ago (1 child) i am not sure which one is the native version... you mean the version packaged by the distro (deb) or the developer (flatpak)? permalink fedilink source parent hideshow 2 child comments replies: [–] liliumstar@lemmy.dbzer0.com 2 points 2 years ago In this case I meant the one packaged by your distro. permalink fedilink source parent
[–] alteredEnvoy@sopuli.xyz 15 points 2 years ago Hmm, wouldn't the virt manager just be a frontend and communicate with the virtd socket though? permalink fedilink source parent
[–] deadcade@lemmy.deadca.de 8 points 2 years ago (2 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] hellostick@lemm.ee [S] 1 point 2 years ago 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) permalink fedilink source parent [–] deafboy@lemmy.world 1 point 2 years ago In my experience, this is not the case. It just says it can't connect. Doesn't specify how or where to. permalink fedilink source parent
[–] hellostick@lemm.ee [S] 1 point 2 years ago 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) permalink fedilink source parent
[–] deafboy@lemmy.world 1 point 2 years ago In my experience, this is not the case. It just says it can't connect. Doesn't specify how or where to. permalink fedilink source parent
[–] hellostick@lemm.ee [S] 1 point 2 years ago (1 child) i am not sure which one is the native version... you mean the version packaged by the distro (deb) or the developer (flatpak)? permalink fedilink source parent hideshow 2 child comments replies: [–] liliumstar@lemmy.dbzer0.com 2 points 2 years ago In this case I meant the one packaged by your distro. permalink fedilink source parent
[–] liliumstar@lemmy.dbzer0.com 2 points 2 years ago In this case I meant the one packaged by your distro. permalink fedilink source parent