bafbbe81c9
The previous commit added a means to generating the completion scripts and this one plugs that into the build system. A new build option 'install_completions' has been introduced. Set to 'True' by default. Completions for bash and fish use pkg-config for getting the preferred install locations for the completions. If the packages are not available, fallbacks are in-place. The 'completion' subdir has been kept to work around the ideology of Meson that does not allow creating/outputing files in subdirectories nor using the output of custom_target() in install_data(). https://github.com/containers/toolbox/pull/840
46 lines
2.5 KiB
Markdown
46 lines
2.5 KiB
Markdown
![README](data/gfx/README.gif)
|
|
|
|
[![Zuul](https://zuul-ci.org/gated.svg)](https://softwarefactory-project.io/zuul/t/local/builds?project=containers/toolbox)
|
|
[![Daily Pipeline](https://softwarefactory-project.io/zuul/api/tenant/local/badge?project=containers/toolbox&pipeline=periodic)](https://softwarefactory-project.io/zuul/t/local/builds?project=containers%2Ftoolbox&pipeline=periodic)
|
|
|
|
[![Arch Linux package](https://img.shields.io/archlinux/v/community/x86_64/toolbox)](https://www.archlinux.org/packages/community/x86_64/toolbox/)
|
|
[![Fedora package](https://img.shields.io/fedora/v/toolbox/rawhide)](https://src.fedoraproject.org/rpms/toolbox/)
|
|
|
|
[Toolbox](https://containertoolbx.org/) is a tool for Linux operating systems,
|
|
which allows the use of containerized command line environments. It is built
|
|
on top of [Podman](https://podman.io/) and other standard container
|
|
technologies from [OCI](https://opencontainers.org/).
|
|
|
|
This is particularly useful on
|
|
[OSTree](https://ostree.readthedocs.io/en/latest/) based operating systems like
|
|
[Fedora CoreOS](https://coreos.fedoraproject.org/) and
|
|
[Silverblue](https://silverblue.fedoraproject.org/). The intention of these
|
|
systems is to discourage installation of software on the host, and instead
|
|
install software as (or in) containers — they mostly don't even have package
|
|
managers like DNF or YUM. This makes it difficult to set up a development
|
|
environment or install tools for debugging in the usual way.
|
|
|
|
Toolbox solves this problem by providing a fully mutable container within
|
|
which one can install their favourite development and debugging tools, editors
|
|
and SDKs. For example, it's possible to do `yum install ansible` without
|
|
affecting the base operating system.
|
|
|
|
However, this tool doesn't *require* using an OSTree based system. It works
|
|
equally well on Fedora Workstation and Server, and that's a useful way to
|
|
incrementally adopt containerization.
|
|
|
|
The toolbox environment is based on an [OCI](https://www.opencontainers.org/)
|
|
image. On Fedora this is the `fedora-toolbox` image. This image is used to
|
|
create a toolbox container that seamlessly integrates with the rest of the
|
|
operating system by providing access to the user's home directory, the Wayland
|
|
and X11 sockets, networking (including Avahi), removable devices (like USB
|
|
sticks), systemd journal, SSH agent, D-Bus, ulimits, /dev and the udev
|
|
database, etc..
|
|
|
|
|
|
## Installation & Use
|
|
|
|
See our guides on
|
|
[installing & getting started](https://containertoolbx.org/install/) with
|
|
Toolbox and [Linux distro support](https://containertoolbx.org/distros/).
|
|
|