c81107b8ac
Currently the images are named as "f<version>/fedora-toolbox". This is troublesome for new users of toolbox (even those with some background to containers) because everywhere the image is advertised or talked about as "fedora-toolbox". This is taken care of by Toolbox CLI but has no effect on Podman itself (or any other tool capable of working with OCI images). Another pain point is in the Fedora registry[0] all "fedora-toolbox" images get a different entry for every version of Fedora. There is no single place for all "fedora-toolbox" images. With this change I propose to only use "fedora-toolbox" as the name of the container and make use of VERSION to distinguish between versions of Fedora. Currently when you go to the Fedora registry and find an entry for "fedora-toolbox" you'll see all previous images. I believe that with this change that "feature" will be lost. But I personally find that "feature" to be rather confusing because what usually a user wants the latest version of a container (I partially base this statement on the fact that most images are versioned this way; e.g. Ubuntu on Docker Hub[1]). [0] https://registry.fedoraproject.org/ [1] https://hub.docker.com/_/ubuntu |
||
|---|---|---|
| Dockerfile | ||
| extra-packages | ||
| missing-docs | ||
| README.md | ||
Toolbox — Unprivileged development environment
Toolbox is a tool that offers a familiar RPM based environment for developing and debugging software that runs fully unprivileged using Podman.
The toolbox container is a fully mutable container; when you see
yum install ansible for example, that's something you can do inside your
toolbox container, without affecting the base operating system.
This is particularly useful on OSTree based Fedora systems like Silverblue. The intention of these systems is to discourage installation of software on the host, and instead install software as (or in) containers.
However, this tool doesn't require using an OSTree based system — it works equally well if you're running e.g. existing Fedora Workstation or Server, and that's a useful way to incrementally adopt containerization.
The toolbox environment is based on an OCI
image. On Fedora this is the fedora-toolbox image. This image is then
customized for the current user to create a toolbox container that seamlessly
integrates with the rest of the operating system.
Usage
Create your toolbox container:
[user@hostname ~]$ toolbox create
[user@hostname ~]$
This will create a container, and an image, called
fedora-toolbox-<your-username>:<version-id> that's specifically customised
for your host user.
Enter the toolbox:
[user@hostname ~]$ toolbox enter
🔹[user@toolbox ~]$