Classic snaps are not parallel installable yet unfortunately.
When using channel (
--channel=..) or mode (
--jailmode) flags, you can only pass a single snap name in the command line.
As for parallel installs of classic snaps, the current state is as @ijohnson wrote, we do not support it at the moment. However, we have some work scheduled to add support for this feature, so things may indeed change in 2-3 releases.
We have discovered one more weird interaction that enabling parallel installs can have with existing snap mount namespaces, see Parallel-instances breaks content snap consumers for details.
With this in mind, I would recommend that if the users ran any snap applications in the currently booted system prior to enabling/disabling the feature, they should reboot after toggling the experimental flag state.
Alternatively they can discard the mount namespace of all snaps, though I see that as something that a snap developer or a snapd hacker would be more willing to try.
Is this still currently the case? It seems to be conflicting with the following passage:
Thanks for spotting. I’ve updated the doc.
The link at https://snapcraft.io/docs/parallel-installs 404s and I’m under the impression that it should be automatically generated from the post here, is there someone who can take a look at restoring it?
Thanks for flagging this, and sorry for the 404. The webteam here at Canonical is experimenting with a new publishing mechanism and this seems to have inadvertently led to a number of 404s for our docs. We’re trying to sort this out now.
On my Thinkpad T510 with 22.04, I’m getting this error when I try to install Firefox beta
$ sudo snap install --beta firefox_beta error: cannot perform the following tasks: - Set automatic aliases for snap "firefox_beta" (cannot enable alias "geckodriver" for "firefox_beta", already enabled for "firefox")
You have the
firefox snap which already provides an alias named
firefox.geckodriver app, so there’s a clear conflict. Try adding
--unaliased when installing
That worked, but what if the app is already installed?
$ sudo snap refresh error: cannot perform the following tasks: - Set automatic aliases for snap "firefox" (cannot enable alias "geckodriver" for "firefox", already enabled for "firefox_beta")
Edit: Uninstalling and reinstalling worked so far.
Would there be detriments for having multiple Firefox instances and one of them installed using the
Do you still need to do:
# sudo snap set system experimental.parallel-instances=true
Doesn’t seem to be necessary anymore.
I just tried with snapd from beta (16778) and it still requires the experimental flag.
snap install hello-world hello-world_foo error: cannot install "hello-world", "hello-world_foo": experimental feature disabled - test it by setting 'experimental.parallel-instances' to true
Ah, you are correct, I had quietly set that earlier and forgot. One wonders whether it’s time for this feature to stop being experimental.
I am using the parallel installs feature to have side-by-side Microsoft Teams accounts (one for each organization I work with). It’s great, but, when Teams is running in the taskbar I have two identical icons (one for each Teams instance) and I cannot quickly differentiate between the two. Also, when I click on a link that is designed to be opened in Teams, I am given a pop-up asking which instance to open. Since the instances have the same title, I cannot tell which one is the correct one.
Is there a way to change the application title and/or icon on a per-parallel-install basis?
I believe the only entity that is suitable for the job are the application developers themselves.
We are considering to use
parallel install feature in our subordinate charms (to provide parallel
pgbouncer installations for different
postgresql clusters inside the same principal
Can you please share plans to remove
experimental flag here?
We are a bit uncomfortable to use experimental feature in production.
I second that idea … I’m currently rewriting Snapcraft 101 course and plan on covering parallel installs, but I’d prefer that that feature not still be listed as experimental.
I’ll “third” how useful parallel installs are: I have, for several years now, kept multiple versions of my snaps installed to facilitate testing and comparison.
I just spoke to the team about the experimental flag with Parallel installs and there are two relatively minor things blocking its removal which we’ll try to prioritise.
The first is that we need to modify the behaviour slightly to not make aliases by default, and then make alias generation optional.
The second is that there were bugs reported some time ago that we’ve been unable to track down. We strongly suspect these have been fixed through other work, but we can hopefully solve this with a call for testing period to ensure there are no serious issues before removing the flag.
I’ll post any further updates here.