a2eeecab3e
- main branch has been deprecated - atomic branch will be where everything is done going forward - moved bunsen build bits out of containers and now layers sit at the repos root - updated build workflow to run on git push - removed more ublue specific's
Main
YA custom Fedora operating system using OCI/Docker containers as a transport and delivery mechanism. Images are rebuit nightly at 23:45 UTC, here is a UTC Clock.
What is this?
My first Linux system that I enjoyed using was CrunchBang Linux, this is what eventually made me switch to linux full time. One of the 'fun' aspects of the distro was using Muppet characters as release names. Using uBlue sericea Bunsen is my layering of features. Eventually I plan on also using base) to build a Hyprland version, Beaker, that I can play around with.
Both have a *-zed option for built in zfs.
Features
- Finish with my quarks
- Remove guest VM support
- Tailscale
- NeoVim
- git
- tmux
- vifm
- Fonts (powerline-fonts, mozilla-fira, fira-code, google-noto, ibm-plex, jetbrains-mono)
How to use these:
To rebase an existing Silverblue/Kinoite machine to the latest release (37):
- Download and install Fedora Silverblue
- After you reboot you should pin the working deployment so you can safely rollback.
- Open a terminal and use one of the following commands to rebase the OS:
Bunsen (Sway derived from Sericea)
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/mitchejj/bunsen:38
or
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/mitchejj/bunsen-zed:38
Beaker (Hyprland derived from Base)
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/mitchejj/beaker:38
ZFS Support
Due to ongoing issues with intergration between the Linux kernel and zfs sometimes the zfs version may not always be up-to-date.
The default mountpoint for a newly created zpool tank is /tank since the
root filesystem is immutable the directory cannot be created. A new mount point
needs to be selected. I would suggest /var/
Verification
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/ublue-os/base
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.