- Shell 88.8%
- Dockerfile 3.9%
- Python 2.9%
- Lua 2%
- Makefile 1.2%
- Other 1.2%
| .tekton | ||
| builds | ||
| Containerfile.d | ||
| hack | ||
| iso | ||
| overlays | ||
| packages | ||
| util | ||
| .containerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .prettierrc | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
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.