v1.0.0 195Docs

Check your installation.

Two quick checks: the image before you boot it, and the machine once you’re in.

01 // BEFORE BOOT

Before you boot

Each image is signed by Ryoku Releases <releases@ryoku.dev>; its signature and checksum prove the file on your disk is the one we built.

  1. 01Import the release key

    Pulls our public release key into your GPG keyring.

  2. 02Confirm the fingerprint

    A signature only counts once you know the key is ours.

    Must printgpg groups it in fours. Every character must match.

  3. 03Verify the image

    Run these where you saved the ISO, its .sig and its .sha256.

What good looks like

gpg: Good signature from "Ryoku Releases <releases@ryoku.dev>"
ryoku-<date>-x86_64.iso: OK

And what it doesn’t

gpg also warns the key is not certified with a trusted signature. That is normal: it only means you never personally signed it. Without Good signature and OK, the file is not ours. Delete it. Do not boot it.

02 // ON THE MACHINE

Once you’re in

Three commands tell you what is installed and whether it is healthy.

  1. 01Match the release

    Confirms this machine matches the release it is on. It changes nothing.

  2. 02Read every health check

    Lists every check without changing anything. Plain ryoku doctor fixes what it safely can.

  3. 03See what is current

    Shows your version, what your channel offers, and any pending updates.

What good looks like

ryoku verify

✓ this box is the machine the release describes

Something still off? ryoku doctor --report writes one shareable report, with no passwords or keys. Bring it to Discord.