Silverblue, and rpm-ostree more generally are moving to HOME=/var/home/$USER and make the /home symlink just a compatibility feature. See: https://github.com/projectatomic/rpm-ostree/pull/1726 Matching what the host does will reduce weird side-effects. Propagate $HOME into the container to avoid mismatches in /etc/default/useradd, and if the host has /home as a symlink to /var/home, do the same for the toolbox. https://github.com/debarshiray/fedora-toolbox/pull/34 |
||
---|---|---|
images/fedora | ||
COPYING | ||
NEWS | ||
README.md | ||
fedora-toolbox | ||
fedora-toolbox-sudo | ||
meson.build |
README.md
Fedora Toolbox — Hacking on OSTree-based Fedoras
Fedora Toolbox is a tool that offers a familiar RPM based environment for developing and debugging software on locked down OSTree based Fedora systems like Silverblue. Such operating systems are shipped as immutable OSTree images, where it's difficult to setup a development environment with your favorite tools, editors and SDKs. A toolbox container solves that problem by providing a RPM based mutable container. You can tweak it to your heart's content and use DNF to install your favorite packages, all without worrying about breaking your operating system.
The toolbox environment is based on 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 Fedora Toolbox container:
[user@hostname fedora-toolbox]$ fedora-toolbox create
[user@hostname fedora-toolbox]$
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 fedora-toolbox]$ fedora-toolbox enter
🔹[user@toolbox ~]$