Skip to main content
Agate is a personal-use image. The customizations reflect one specific setup and may not suit your hardware or workflow. Review the Introduction before rebasing to understand what is included.
Rebasing replaces your entire OS image. Your home directory and layered packages are preserved, but your base system will switch to Agate. Make sure you have a backup or are comfortable with the rollback process before proceeding.
1

Check prerequisites

You need a running Fedora Atomic, Silverblue, or Bazzite system with rpm-ostree available. Verify with:
rpm-ostree --version
If the command is not found, your system does not support rpm-ostree rebasing.
2

Choose a registry

Agate images are published to two registries. Use Quay.io as the primary source. The GitHub Container Registry is available as a mirror if Quay.io is unreachable.
RegistryImage
Quay.io (primary)quay.io/fptbb/agate:latest
GitHub (mirror)ghcr.io/fptbb/agate:latest
3

Run the rebase command

Pick the registry you want to use and run the corresponding command.
sudo rpm-ostree rebase ostree-unverified-registry:quay.io/fptbb/agate:latest
rpm-ostree will pull the image and stage it as the next boot deployment. This may take several minutes depending on your connection speed.
4

Reboot

After the rebase completes, reboot to boot into Agate:
systemctl reboot
5

Check deployment status

After rebooting, confirm you are running Agate:
sudo bootc status
The output shows the current booted image, its digest, and any staged updates.
6

Verify the image (optional)

For additional confidence in image integrity, verify the signature with cosign. See the Verification page for full instructions.
cosign verify --key https://os.fpt.icu/cosign.pub quay.io/fptbb/agate
Last modified on April 7, 2026