Skip to content

Latest commit

 

History

History
44 lines (28 loc) · 2.08 KB

README.md

File metadata and controls

44 lines (28 loc) · 2.08 KB

TODO: Branch for versions Make stable version of image, which follows the creation of a new versioned branch, like bazzite. this version should be reflected in the system. Reset rechunker on each feature addition number change, or major upstream version change something like 40.feature addition number.minor bugfix number

TODO: Build separate isos for all image variants

Container Signing

Container signing is important for end-user security and is enabled on all Universal Blue images. It is recommended you set this up, and by default the image builds will fail if you don't.

This provides users a method of verifying the image.

  1. Install the cosign CLI tool

  2. Run inside your repo folder:

    cosign generate-key-pair
    • Do NOT put in a password when it asks you to, just press enter. The signing key will be used in GitHub Actions and will not work if it is encrypted.

Warning

Be careful to never accidentally commit cosign.key into your git repo.

  1. Add the private key to GitHub

    • This can also be done manually. Go to your repository settings, under Secrets and Variables -> Actions image Add a new secret and name it SIGNING_SECRET, then paste the contents of cosign.key into the secret and save it. Make sure it's the .key file and not the .pub file. Once done, it should look like this: image

    • (CLI instructions) If you have the github-cli installed, run:

    gh secret set SIGNING_SECRET < cosign.key
  2. Commit the cosign.pub file into your git repository