Is there a way to make silverblue declarative, something like Nix OS?

Ask Fedora
, , , ,
1

like is possible to make another computer that im installing a new silverblue, be like the current one im working on In a easy way ?

2

Added config, desktop-configuration, installation, nix

3

For the host system, this would be using a Containerfile and building your custom system yourself. Here you can also add files to /usr and /etc

For the user part, you might be able to use nix or something else.

For mutable distrobox containers, you can use distrobox-compose with a compose file too

2 Likes
4

one doubt, i though on something similar this, but im my understand i would branch off fedora right ?

if i do a custom image i wouldnt be able to keep upgrading, rebasing with the fedora images because would lost the custom stuffs, if i understand right

is possible to do a custom container that could keep on track with fedora ?

5

Yes, but it’s still not official and therefore not documented, at least for Fedora Silverblue.

See What’s new for Fedora Atomic Desktops in Fedora 41 - Siosm’s blog.

1 Like
6

I dont get your question.

If you build a custom bootable OCI container image, this bases off fedora.

Secureblue now bases off the quay.io Fedora OCI images that siosm builds. Unlike basing off ublue *-main like blue-build would suggest.

These are pulled by a github worker script, built on their environment and made into an image. You have set ghcr.io, the Github container registry, as your remote for your system and rpm-ostree or bootc update from that image.

You will always keep track of fedora, with your image as the intermediary, as it is a downstream.

Only on version upgrades you need to change the containerfile to use the new fedora version. Not sure how this is done tbh