Bi saw some comments in a PR
Bwe have too many conversations, please 
Hyeah i didnt find an existing thread and i forget there is a button in the top now to make threads
Hi figured since we are adding toolbox support we could at least give it the same treatment as distrobox with menus and such
so thats what i have been working on this evening, and if you spot in the last command it automatically detect if its a image or image registry
so thats what i have been working on this evening, and if you spot in the last command it automatically detect if its a image or image registry
H
Honly thing left now is the rhel image detection to do the login stuff. as i am not sure if its the same podman login command that @Noel used for distrobox
BHyes
Hdo you think we should make
toolbox.ini point to our ublue toolbox images?Hor the quay ones or just keep them rhel+fedora+ubuntu+arch only 
Bwell...
Bplease don't take this as an attack.... but I actually think the toolbox assemble stuff is a bit over-engineered...
The only thing we really needed toolbox for was RHEL and maybe Fedora toolboxes.
The only thing we really needed toolbox for was RHEL and maybe Fedora toolboxes.
Hsince the benefit with the ublue ones (at a glance from me who dont use toolbox) is that they have a latest tag so we dont need to update the registry url
BThat said, if it's simple enough, i'm not against it... just uncertain of the value add.
Hi just made it as a nice to have for those who want to use toolbox
BI understand and appreciate the effort. But the original request was pretty narrow in scope... it's creeped a bit.
BSo, how can my comments be helpful?
BI'd take them as input about keeping the toolbox "tooling" simple. That includes limiting the number of toolboxes available through it to RHEL and maybe Fedora.
Halso the other reason i made the assemble function is because its dead easy to update without modifying the script itself 
BI'm open to being challenged... but if anything I'm just sharing a perspective.
BDefinitely lets keep the list of images for toolbox short. We aren't trying to add all of distrobox capability to toolbox, so we shouldn't try to fit all the same image options in both.
Hwell yeah we wanted to limit the images used for it just curious if we want the pre-defined ones to point to quay latest images for fedora? redhat ones will be the redhat access ones
Hoh yeah thats not the plan, if i were going to make an assemble function it was going to be a severely limited implementation especially since toolbox lacks a lot of functionality
Hi just liked the idea of just being able to
ujust toolbox-assemble file.ini and then assemble all the containers in it or select one to assemble in case it would be usefulHhow does that look?
Bi think that looks like the right place to start
Hidk if there is anything equivalent to fedora:latest for toolbox without using our own image but it also serves as a nice demonstration of the ini file four our toolbox assemble
Hi will get to making the just commands now since the tooling is done at least for just (and it will not be expanded upon)
Hhey @Noel i am correct to believe you still use
podman login for the rhel images when using toolbox right?
NSo it may not be required anymore.
NRHEL is available straight through toolbox and that registry doesn't require authentication.
NI looked at the container files and they are identical.
NWhat you need to use them is a dev subscription or full subscription through Red Hat.
NThat is accomplished through subscription-manager.
NI've found it the easiest to layer that into my image.
Hok so leave that to the user then?
Hor shall we make the just recipe layer subscription manager if they try to make a rhel container
Bi think that's a task for the user
Bif they need subscription manager, they should be able to configure it
Hok wow, this made my task way easier then
NYup!
Hall this code
Hgone
NLike I said, it was debatable whether it's worth having.
BKISS
NEither way, it's a convenience thing. And that's what ujust is for in a lot of cases.
BKISS - "Keep It Simple S(ubstitute noun starting with 's' here)"
Bi tell myself this often
Hsame, except when i start overengineering things to protect from S(ubstitute noun starting with 's' here) stuff
Bi also try to remember... if software and open source is about freedom... i'm not trying to protect users from hurting themselves... that's the cult of safety and it leads to reduced freedom...
but... i also try to balance that with not creating tools which are deliberately difficult and likely to cause problems
but... i also try to balance that with not creating tools which are deliberately difficult and likely to cause problems