37d5459bfe
There's no easy way to introspect the Kerberos configuration from the command line. eg., the credential cache type being used, or the value of the socket_path setting that denotes which socket the KCM service will listen on. Therefore, it's assumed that the former is KCM if the socket's path can be parsed from the sssd-kcm.socket unit. Given the immutable nature of Podman containers, the toolbox container and its corresponding image will have to be re-created if the host OS is sufficiently re-configured. The krb5-libs package was added to the base toolbox images to ensure the presence of the /etc/krb5.conf.d directory with the correct permissions. Currently, the package is already pulled in by various dependencies. Therefore, it doesn't increase the size of the base image, but serves as a safeguard against any inadvertent changes. https://github.com/debarshiray/toolbox/pull/74 |
||
|---|---|---|
| data | ||
| doc | ||
| images/fedora | ||
| COPYING | ||
| gen-docs-list | ||
| meson.build | ||
| NEWS | ||
| README.md | ||
| toolbox | ||
| toolbox-sudo | ||
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 ~]$