| 1 |
 |
| 2 |
|
| 3 |
[](https://softwarefactory-project.io/zuul/t/local/builds?project=containers/toolbox) |
| 4 |
[](https://softwarefactory-project.io/zuul/t/local/builds?project=containers%2Ftoolbox&pipeline=periodic) |
| 5 |
|
| 6 |
[](https://www.archlinux.org/packages/community/x86_64/toolbox/) |
| 7 |
[](https://src.fedoraproject.org/rpms/toolbox/) |
| 8 |
|
| 9 |
[Toolbox](https://containertoolbx.org/) is a tool for Linux, which allows the |
| 10 |
use of interactive command line environments for development and |
| 11 |
troubleshooting the host operating system, without having to install software |
| 12 |
on the host. It is built on top of [Podman](https://podman.io/) and other |
| 13 |
standard container technologies from [OCI](https://opencontainers.org/). |
| 14 |
|
| 15 |
Toolbox environments have seamless access to the user's home directory, |
| 16 |
the Wayland and X11 sockets, networking (including Avahi), removable devices |
| 17 |
(like USB sticks), systemd journal, SSH agent, D-Bus, ulimits, /dev and the |
| 18 |
udev database, etc.. |
| 19 |
|
| 20 |
This is particularly useful on |
| 21 |
[OSTree](https://ostree.readthedocs.io/en/latest/) based operating systems like |
| 22 |
[Fedora CoreOS](https://coreos.fedoraproject.org/) and |
| 23 |
[Silverblue](https://silverblue.fedoraproject.org/). The intention of these |
| 24 |
systems is to discourage installation of software on the host, and instead |
| 25 |
install software as (or in) containers — they mostly don't even have package |
| 26 |
managers like DNF or YUM. This makes it difficult to set up a development |
| 27 |
environment or troubleshoot the operating system in the usual way. |
| 28 |
|
| 29 |
Toolbox solves this problem by providing a fully mutable container within |
| 30 |
which one can install their favourite development and troubleshooting tools, |
| 31 |
editors and SDKs. For example, it's possible to do `yum install ansible` |
| 32 |
without affecting the base operating system. |
| 33 |
|
| 34 |
However, this tool doesn't *require* using an OSTree based system. It works |
| 35 |
equally well on Fedora Workstation and Server, and that's a useful way to |
| 36 |
incrementally adopt containerization. |
| 37 |
|
| 38 |
The toolbox environment is based on an [OCI](https://www.opencontainers.org/) |
| 39 |
image. On Fedora this is the `fedora-toolbox` image. This image is used to |
| 40 |
create a toolbox container that offers the interactive command line |
| 41 |
environment. |
| 42 |
|
| 43 |
Note that Toolbox makes no promise about security beyond what's already |
| 44 |
available in the usual command line environment on the host that everybody is |
| 45 |
familiar with. |
| 46 |
|
| 47 |
|
| 48 |
## Installation & Use |
| 49 |
|
| 50 |
See our guides on |
| 51 |
[installing & getting started](https://containertoolbx.org/install/) with |
| 52 |
Toolbox and [Linux distro support](https://containertoolbx.org/distros/). |