You can check your installed instances, and you will see the whole gamut of versions: snap list| grep vlc vlc 3.0.7 1049 stable videolan* - vlc_edge 4.0.0-dev. Or you can even directly install a different version as a separate instance: snap install -candidate vlc_second vlc_second (candidate) 3.0.7 from VideoLAN✓ installed If you already have multiple instances installed, you can just refresh one of them, e.g.: the aptly named vlc_edge instance: snap refresh -edge vlc_edge VLC is a good example, with stable version 3.0.7 available, and preview version 4.0.0 in the edge channel. So if you want to test different versions – which can really be helpful if you want to learn (and prepare for) what new editions of an application bring, you can do this in parallel to your production setup, without requiring additional hardware, operating system instances, users – or having to worry about potentially harming your environment. Not only can you have multiple instances, you can manage the release channel of each instance separately. For instance: snap remove odio_second odio_second removed Different instances, different versions You can remove each one using its full name (including the identifier), connect and disconnect interfaces, start and stop services, create aliases, and more. snap install odio_first odio_second odio_second 1 from Canonical✓ installed odio_first 1 from Canonical✓ installedįrom here on, you can manage each instance in its own right. Snapd will only download the snap package once, and then configure the two requested instances separately. For example, let’s setup two instances of odio. You can try parallel installs with any snap in the store. In fact, this may be the preferred way, as you will be able to clearly tell your different instances apart. snap install vlc) and then use unique identifiers for your test installs only. You can install a production version (e.g. You can install them each individually or indeed in parallel, e.g. You have quite a bit of freedom choosing how you use this feature. Technically, gimp_first does not exist as a snap, but snapd will be able to interpret the format of “snap name” “underscore” “unique identifier” and install the right software as a separate instance. For example, if you want to install GIMP with your own identifier, you can do something like: snap install gimp_first This is a manual step, and you can choose anything you like for the identifier. The identifier is an alphanumeric string, up to 10 characters in length, and it is added as a suffix to the snap name. Now, the actual setup may appear slightly counter-intuitive, because you need to append a unique identifier to each snap instance name to distinguish them from the other(s). Once this step is done, you can proceed to installing software. The first step is to turn on a special flag that lets snapd manage parallel installs: snap set system experimental.parallel-instances=true Experimental features & unique identifier With snaps, this is a fairly simple task.įrom version 2.36 onwards, snapd supports parallel install – a capability that lets you have multiple instances of the same snap available on your system, each isolated from the others, with its own configurations, interfaces, services, and more. If you want to test multiple instances, you will most likely need to configure the remainder yourself. While the repository channels offer great availability to software, you can typically only install a single instance of an application. In Linux, testing software is both easy and difficult at the same time. Parallel installs – test and run multiple instances of snaps
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |