Dive into Toolbx on our test day, which is only happening today! Details on how to contribute are below. The @containertoolbx team will be grateful for all the testing they can get!
If you use Fedora Atomic Desktops or Fedora CoreOS, this may be a neat account to follow as it's what we use to manage containers - an important part of how to use this kind of system.
Toolbx is now on Mastodon! Follow along and become part of a community that's passionate about using containers to revolutionize their development and troubleshooting experience on Linux. #introduction#toolbx
I had a good one-year run with #Fedora#Silverblue, but for business reasons I had to revert back to regular/standard Fedora. I did learn a lot, though. For example, I'll keep using #Toolbx (#Toolbox?) as part of my development workflow. I do believe immutable distros have their place, and are very appreciated, but some of their limitations are very hard to deal with when you have a very chaotic workflow like mine, that requires a lot of context switching and new tool testing.
I missed this, but you can now use Ubuntu images in Toolbx! I know distrobox exists, but Toolbx ships with Endless OS, so this is relevant to my interests. 😃
Also, reminder that today is the Test Day for Toolbx specifically. It's a release blocker now, so consider helping us make this a smooth process! #Fedora#Toolbx#Linux
Please support Fedora with testing the latest kernel from Sep 10-17.
We also have Toolbx. 🧰 It has been a made a release-blocking deliverable for Fedora, so we really want to iron out bugs so that it doesn't hold up Fedora 39. Test Day for this is Sep 14.
I have made another release of #Linux Desktop Migration Tool.
You can now easily migrate your #Toolbx containers to a new machine with it! Reinstalling #Flatpak apps is also more robust now.
Fooling around with #container technology, #Flatpak and #toolbx again, together with #vscode on #fedora#silverblue. The "current" approaches seem to either be using a lot of custom scripting and hooks with https://github.com/owtaylor/toolbox-vscode/ or try to hook into the toolbx container through VS Code's "Dev Containers" feature using com.visualstudio.code.tool.podman. The former is highly complex and (IME) prone to breakage, the latter runs into a lot of limitations. There's finally the option to install VS Code within the toolbox but that's kinda... ugh.
While toying around I noticed that I don't actually want to have the VS Code "run" or "connect" to the toolbx. Actually, I only want to have the integrated VS Code terminal "run" in the context of the toolbx, the "actual development" would either happen through the standard Dev Container feature with a container *for that project *(instead of re-using the toolbx container) or using Flatpak SDKs with the Flatpak extension, if publishing directly trough Flatpak like GNOME Builder does.
Prefer using Island Of TeX #container -s for #ConTexT or #TeXLaTeX interactive development but don't want to type that much? You can simply create an alias, shell function or a simple script -- called e.g., context -- in your $PATH:
Seriously, #distrobox just keeps getting better and better the more I learn about it. This one upgrades every container you've created with one single command.
I'd like to write migration scripts to move data from the old laptop to the new one. It would move #flatpak app data over, reinstall flatpaks there, move #Toolbx containers, perhaps desktop settings, too.
But maybe something like that already exists and I don't have to start from scratch. Any idea?