Toolbox in Silverblue version 31.20191111.0 (2019-11-11T00:35:35Z)
37c730f97d9c8c2bcb43f513c3aba72ce88b511d13a5f8ef86798f2788d28d5f works for me.
Upgrading to 31.20191112.0 (2019-11-12T00:37:19Z)
e26beb4354049bd5b361d1a9c3fd047c92d51a04e16b4e3c2b925df46136f285 pulls in a new crun (and kernel) and toolbox no longer can run or create containers… again.
crun was upgraded from
crun-0.10.5-2.fc31; something in the commit breaks toolbox here.
Using Silverblue is generally great. What’s not great is the random breakage of toolbox and everything it depends upon (podman, crun/runc, etc.). This happened during pre-beta and beta versions of Fedora (which is annoying), but, sadly, it’s also happening post-release too.
Could we have some sort of automated testing which verifies that toolbox can create (and run) new containers and also run existing ones before the Silverblue version is bumped publicly please?
So many people using Silverblue depend on Flatpak and toolbox working. Randomly being without one or the other really throws a wrench in things. (Thankfully, I haven’t had an issue with Flatpak on Silverblue yet. Whew.)