No description
  • Shell 88.9%
  • Dockerfile 3.9%
  • Python 3%
  • Lua 1.9%
  • Makefile 1.1%
  • Other 1.2%
Find a file
James Harmison 9ee7b7fc82
Some checks failed
Pipelines as Code CI / citrus Failed
Pipelines as Code CI / steam Success
Pipelines as Code CI / desktop Success
fix: caffeine configs
2026-10-06 14:56:16 -04:00
.tekton remove: kernel swap 2026-10-04 21:02:34 -04:00
builds fix: no more custom kernel 2026-10-02 20:45:19 -04:00
Containerfile.d fix: kernel version handling, remove some testing things interfering 2026-10-06 12:23:46 -04:00
hack fix: improve config-diff to identify files whose changes are only metadata 2026-09-18 20:25:38 -04:00
iso update: make vm creation easier 2026-07-29 13:15:24 -04:00
overlays fix: caffeine configs 2026-10-06 14:56:16 -04:00
packages fix: no more custom kernel 2026-10-02 20:45:19 -04:00
util remove: kernel swap 2026-10-04 21:02:34 -04:00
.containerignore add: .containerignore 2026-05-07 22:30:16 -04:00
.gitattributes overlays/gui-system/usr/share/backgrounds/bulletpair-darkmatter.png: convert to Git LFS 2025-11-15 07:33:17 -05:00
.gitignore update: make vm creation easier 2026-07-29 13:15:24 -04:00
.prettierrc docs: clean up multiple elements of the documentation to support no public registry 2026-01-16 16:29:46 -05:00
LICENSE fix: remove LICENSE notice for removed code 2025-10-25 19:56:38 -04:00
Makefile remove: kernel swap 2026-10-04 21:02:34 -04:00
README.md update: make vm creation easier 2026-07-29 13:15:24 -04:00

bootc-image

This is the code to build the bootc-based Fedora Remix I use on multiple computers. There's a variant for my desktop, laptop, etc. and a different variant for my TV PC, like a heavily customized SteamOS or Bazzite. There's a couple of really bad reasons for this (I am a control freak and a technology nerd and I like having deeply customized setups), but also a couple of really good reasons (I work with bootc-based technology as my day job and keeping myself engaged in it keeps me sharp).

Using bootc in particular allows me to ensure I have a consistent experience on every machine, without a dotfiles repo, and without configuration drift (or, at least with measurable and recoverable configuration drift - check out config-diff.sh).

Can I use this?

Sure! My image is published at registry.apps.leidos.quadframe.dev/bootc-image/bootc-image:desktop (with other builds on other tags). You can also edit anything to your heart's content and create tmp/auth.json with a podman authfile for your registry, then run make IMAGE=yourregistry/yourimage:yourtag USER=youruser and it'll build, rechunk, and publish the image, if you have the dependencies installed. Check the Makefile and iso/iso.mk for more details on other variables you can override to affect the build behavior. make iso IMAGE=yourregistry/yourimage:yourtag should roll an installer ISO for you, but you'll want to override some other variables for that one for sure (like setting a user or LUKS password).

You're also welcome to steal snippets of my code that are useful to you. If you don't know how to use the image directly, probably just "borrow" the useful code.