This is a personal distrobox container image. I used the https://github.com/ublue-os/boxkit template to build it.
A base image and action for Toolbx and Distrobox. Sure, you can use the distro you're used to, but what if ...
This image is going to experiment with what a "born from cloud native" UNIX terminal experience would look like. It is used in conjuction with a dotfile manager and designed to be the companion terminal experience for cloud-native desktops. We're starting small but have big aspirations.
- Starts with the latest Alpine image from the Toolbx Community Images
- Adds some quality of life
starship
prompt for that <3just
for task executionchezmoi
for dotfile managementbtop
for process managementmicro
andhelix
text editors- clipboard to cut, copy, and paste anything, anywhere, all from the terminal!
python3
- Some common power tools:
plocate
,fzf
,cosign
,ripgrep
,github-cli
, andffmpeg
- CLI tools recommended by rawkode
- Host Management QoL
- These are meant for occasional one off commands, not complex workflows
- Auto symlink the flatpak, podman, and docker commands
- Auto symlink rpm-ostree for Fedora
- Auto symlink transactional-update for openSUSE MicroOS
- These are meant for occasional one off commands, not complex workflows
If you use distrobox:
distrobox create -i ghcr.io/sschmeier/boxkit -n boxkit --pull
distrobox enter boxkit
If you use toolbx:
toolbox create -i ghcr.io/sschmeier/boxkit -c boxkit
toolbox enter boxkit
Use chezmoi
to pull down your dotfiles and set up git sync.
I recommend using the origianl template at https://github.com/ublue-os/boxkit
Fork and add programs to this this image - over time you'll end up with the perfect CLI for you. Keeping it as a pet works, though the author recommends leaving all your config in git and routinely pulling a new image.
The user experience is much nicer if you set your terminal open right in the container and is the intended experience.
These images are signed with sisgstore's cosign. You can verify the signature by downloading the cosign.pub
key from this repo and running the following command:
cosign verify --key cosign.pub ghcr.io/sschmeier/boxkit
If you're forking this repo you should read the docs on keeping secrets in github. You need to generate a new keypair with cosign. The public key can be in your public repo (your users need it to check the signatures), and you can paste the private key in Settings -> Secrets -> Actions. Create a repository key names SIGINING_KEY