8000 GitHub - Venefilyn/veneos: Bootc images based on Fedora Atomic & Fedora CoreOS
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Venefilyn/veneos

Repository files navigation

Artifact Hub Build VeneOS Build VeneOS ISO

VeneOS - Venefilyn OS

A custom Fedora Atomic image designed for gaming, development and daily use. Based on Bazzite Gnome using https://github.com/ublue-os/image-template

Primarily intended for myself.

Variants/tags

Desktop

  • Built on Fedora Atomic 42
  • Uses Bazzite as the base image
  • GNOME 48
  • Optimized for AMD GPU

Server

Features

  • Bazzite features
  • Curated list of Flatpaks
  • Starship prompt, Fish, fuck alias and Atuin history search (Ctrl+R). Started through zsh
  • NodeJS and front-end tooling
  • Setup command for git to work with SSH auth, SSH signing, and to work within containers without extra configuration

Install

Image Verification

All my images are signed with sigstore's cosign. You can verify the signature by running the following command:

cosign verify --key https://github.com/Venefilyn/veneos/raw/main/cosign.pub ghcr.io/veneos/IMAGE:TAG

Desktop

From existing Fedora Atomic/Universal Blue installation switch to VeneOS image:

sudo bootc switch --enforce-container-sigpolicy ghcr.io/venefilyn/veneos:latest

If you want to install the image on a new system download and install Bazzite ISO first:

https://download.bazzite.gg/bazzite-stable-amd64.iso

Server

Existing installation

Note

Do verify the image first to make sure it matches

From existing Fedora CoreOS installation, first rebase to one unverified registry

sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/IMAGE:TAG

Now we have the container signatures and can use the signed one

sudo rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/IMAGE:TAG

New installation

For a completely new system, we follow examples/veneos-server-autorebase.butane template.

  1. Follow CoreOS docs for setting up both the password and SSH key authentication.
  2. Generate an Ignition file for the CoreOS installation using the Butane file
    podman run --interactive --rm quay.io/coreos/butane:release \
          --pretty --strict < veneos-server-autorebase.butane > veneos-server-autorebase.ign
  3. Verify it works by installing CoreOS for bare-metal inside a VM. Remember to share and mount the .ign file if you use ignition file or allowing access to host's local network.
  4. Run sudo coreos-installer install /dev/sda-or-other-drive --ignition-url https://example.com/veneos-server-autorebase.ign (or --ignition-file /path/to/veneos-server-autorebase.ign). Your ignition file should work for any platform, auto-rebasing to the veneos-server:stable (or other IMAGE:TAG combo), rebooting and leaving your install ready to use.
  5. Reboot the VM and verify the installation.
  6. If it all works, repeat the bare-metal installation steps but for your server as we can now be relatively sure it works.

Custom commands

The following ujust commands are available on top of most ublue commands:

# Install all VeneOS apps
ujust vene-install

# Install Flatpaks
ujust vene-install-flatpaks

# Setup VeneOS terminal configs
ujust vene-setup-cli

# Setup git
ujust vene-setup-git

Package management

GUI apps can be found as Flatpaks in the Discover app or FlatHub and installed with flatpak install ....

Acknowledgments

This project is based on the Universal Blue image template and builds upon the excellent work of the Universal Blue community.

Repository created with inspiration from multiple different bootc repositories

Releases

No releases published

Packages

 
 
 

Contributors 2

  •  
  •  
0