:placard: Navigating the Waters: Installing Software in Qubes

Installing software in Qubes OS can be a daunting experience. This guide's goal is to serve as a crossroad sign to help you navigate this landscape.

crossoroads_qubes|536x500

(image credit: @deeplow, via public domain, original from pixabay)

Installing in a template

Will be available to all qubes based on the template. Updates via routine updates (normal way of updating).

[details="other methods (advanced)"]

> ⚠️ This is for advanced users only

Using the updates proxy to give software management programs internet access in the template.

In case this software installs stuff in non-persistent directories you'll need to use bind-dirs those directories persist when starting an app qube based on the template.

Examples of what can be achieved with this - pip install in template - https://forum.qubes-os.org/t/external-repositories-pip-snap-appimage-persistent-installations-in-template-appvm/561/4 [/details]

Installing in your app qube

Will only be available in the app qube where you installed it.

> ⚠️ Updates are simple but manual (one click for qube apps and one-command for snap packages.

Qube Apps - developed by Micah Lee, a trusted community member.

Installing in a dedicated qube (versatile)

Standalone qubes are dedicated qubes. If you want to install random software that you don't trust to be installed on your main templates and only really need to use in a single qube, this is probably the way to go. It's very flexible. The only downside really is it occupies a lot of space (like regular templates) but none of the advantages of splitting that space among app qubes.

Regardless, the security isolation and flexibility may make this a way to go for very particular pieces of software.

You can install stuff as if you were in a template see the first section