ce69f99a2bf9adaf747848c2a413238b5802ab20
All checks were successful
bluebuild / Build Custom Image (recipe.yml) (pull_request) Successful in 1m50s
bluebuild / Build Custom Image (recipe_nvidia.yml) (pull_request) Successful in 6m27s
bluebuild / Build Custom Image (recipe.yml) (push) Successful in 5m16s
bluebuild / Build Custom Image (recipe_nvidia.yml) (push) Successful in 7m24s
hydro-os 
This is a personal OS distro that I am using to learn more about the technolgies behind Bluebuild and possibly to later learn about hosting a git server, container repositiories, and actions.
Installation
Warning
This is an experimental feature, try at your own discretion.
To rebase an existing atomic Fedora installation to the latest build:
- First rebase to the unsigned image, to get the proper signing keys and policies installed:
rpm-ostree rebase ostree-unverified-registry:git.hydrosaber.com/eriq12/hydro-os:latest
- Reboot to complete the rebase:
systemctl reboot
- Then rebase to the signed image, like so:
rpm-ostree rebase ostree-image-signed:docker://git.hydrosaber.com/eriq12/hydro-os:latest
- Reboot again to complete the installation
systemctl reboot
The latest
tag will automatically point to the latest build. That build will still always use the Fedora version specified in recipe.yml
, so you won't get accidentally updated to the next major version.
Attribution
Thanks to Wayblue for how to get around some issues with sddm on an atomic distribution and how to create a working distro from the base Fedora image.
Description
No description provided
atomicbluebuildbluebuild-imagecustom-imageimage-basedimmutablelinuxlinux-custom-imageocioci-imageoperating-system
Readme
Apache-2.0
500 KiB
Languages
Shell
100%