feat(just): Add RHEL Toolboxes and UBI I...
GitHub
feat(just): Add RHEL Toolboxes and UBI Images by noelmiller · Pull ...
This is to fix: #106
I decided to go with the official toolbox images for RHEL which will require users to log in. I did add a check to confirm the user is logged in to registry.redhat.io before at...
16 Replies
i added comments on the issue and PR... happy to discuss in thread here or on github 🙂
thank you for putting it together! I hope it's clear, I think it's perfect except for the question of using distrobox vs toolbox (or both)
Yeah, I just posted on github.
I'm not as familiar with Toolbox as I am with distrobox.
i shared my thoughts there, but for the sake of musing... i'll do my musing here 🙂
i have an "ideal" concept that instead of "distrobox-foo" we could just do "box-foo" recipe names, which default to distrobox, but either setting a variable for long term choice, or passing a cli arg for single choice, would use toolbox instead
however, the
distrobox-foo name is quite established, so changing it may be unwisemight be worth considering making them a list of choices? https://github.com/ublue-os/config/pull/181
Would definitely shorten the
just -li'm open to exploring things... just don't want to loose toolbox users as we try to invite redhatters to use this
Absolutely. What is the relation of distrobox to toolbox?
i'm looking at you. i hope you feel welcome 😉 because we need you
lol i'm selfish like that
I seem to have both on bluefin and they open the same set of podman containers 😄
no formal relationship.
distrobox is a collection of bash scripts
toolbox is a Go binary tool
distrobox is more distro agnostic
toolbox can run other images, but has primarily been developed for CoreOS-like systems by RedHat related folks, i think
they do the same basic thing, but a bug fixed in one is not fixed in the other, and as time goes on, i think features have diverged slightly, though occasionally, something gets created in one from the other...
example: i don't think it was as easy to use non-redhat/fedora images until after distrobox was on the scene and then some changes got added to toolbox
yes, both can use same images today... and in fact, i think one can argue that distrobox is a more specific implementation of toolbox? it least, it labels it's containers with
toolbox as well as distroboxGot it. Yeah, for Red Hat folks, they are likely to prefer toolbox. And it's everywhere in the documentation, I've just not really played with it too much.
And really, any coreos/silverblue user is more likely to know it, as it's the default.
if they read docs
for sure.
A environment variable to switch between is probably a good idea.
GitHub
provice option to use toolbox in our distrobox just recipes · Issue...
Giving users a choice definitely is better in my opinion (but I think we should default to distrobox). I agree, mostly from the position that our just recipes are all, already distrobox-* Is it pos...
i tweaked that issue a little more, i'll probably leave it for now, not my priority today, but wanted to give your PR attention
distrobox also has some convenience scripts out of the box that toolbox doesn't have. Distrobox will create a desktop entry for launching the container, easy export of binaries, services, and apps to the host, aseemble files, and running host binaries from the box. Toolbox can do all of those as well, but requires some manual setup.
I think the only major difference right now is that distrobox supports alternative container homes and toolbox doesn't.
yeah, feature-wise, i think you hit the big differences @M2 :
- easy export of container binaries, services & desktop entries
- alternative container homes
i know recently the Prompt terminal exposed some differences in how they handle some character... escape char maybe? something related to that...
that's the kind of detail that's annoying... i think toolbox is better on that one
i'm mostly just happy to provide the choice though, not debating what is objectively better