Skip to content
/ freaky Public
generated from blue-build/template

My personal image with GNOME, Steam, and ROCM 7.1

License

Notifications You must be signed in to change notification settings

tduarte/freaky

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

39 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

freaky   bluebuild build badge

See the BlueBuild docs for quick setup instructions for setting up your own repository based on this template.

After setup, it is recommended you update this README to describe your custom image.

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:ghcr.io/tduarte/freaky:latest
    
  • Reboot to complete the rebase:
    systemctl reboot
    
  • Then rebase to the signed image, like so:
    rpm-ostree rebase ostree-image-signed:docker://ghcr.io/tduarte/freaky: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.

ISO

If build on Fedora Atomic, you can generate an offline ISO with the instructions available here. These ISOs cannot unfortunately be distributed on GitHub for free due to large sizes, so for public projects something else has to be used for hosting.

Local Testing

You can test builds locally before pushing to CI using the BlueBuild CLI.

Quick Start

  1. Install BlueBuild CLI:

    ./scripts/local-build.sh install

    Or manually:

    podman run --pull=always --rm ghcr.io/blue-build/cli:latest-installer | bash
    # or with docker:
    docker run --rm ghcr.io/blue-build/cli:latest-installer | bash
  2. Generate Containerfile (optional, for inspection):

    ./scripts/local-build.sh generate
  3. Build locally:

    ./scripts/local-build.sh build

    Or with a custom tag:

    ./scripts/local-build.sh build freaky:test
  4. Test the built image:

    podman run --rm -it freaky:local /bin/bash
    # or with docker:
    docker run --rm -it freaky:local /bin/bash

Using Distrobox (Alternative)

If you prefer to use distrobox instead of installing BlueBuild directly:

# Create a distrobox container with BlueBuild
distrobox create -i ghcr.io/blue-build/cli:latest -n bluebuild

# Enter the container
distrobox enter bluebuild

# Build from inside the container
cd /path/to/freaky
bluebuild build ./recipes/recipe.yml --tag freaky:local

Manual BlueBuild Commands

If you have BlueBuild CLI installed, you can also use it directly:

# Generate Containerfile
bluebuild generate ./recipes/recipe.yml -o Containerfile

# Build image
bluebuild build ./recipes/recipe.yml --tag freaky:local

# Test the image
podman run --rm -it freaky:local /bin/bash

For more information, see the BlueBuild local testing documentation.

Verification

These images are signed with Sigstore's cosign. You can verify the signature by downloading the cosign.pub file from this repo and running the following command:

cosign verify --key cosign.pub ghcr.io/tduarte/freaky