From 0e4f3f96e787915293ec1fa2e4ee76ca36e7fa6d Mon Sep 17 00:00:00 2001 From: joshuaaferguson Date: Sun, 26 Apr 2026 07:21:08 -0700 Subject: [PATCH] =?UTF-8?q?docs(README):=20retract=20"image=20not=20publis?= =?UTF-8?q?hed"=20warning=20=E2=80=94=20chrome-selkies=20is=20live?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Six iterations later (streamspace-templates#4 #5 #6 #7), the image build pipeline actually publishes: ghcr.io/streamspace-dev/chrome-selkies:latest - linux/amd64 (arm64 blocked on upstream Selkies binaries) - cosign keyless signature - SPDX SBOM attestation Drop the WARN block from "Available applications" in the README and list chrome-selkies as the current published image. Add a note that the GHCR package is private by default; the org admin needs to flip it to public for anonymous pulls. --- README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 2d75a48..49e43ea 100644 --- a/README.md +++ b/README.md @@ -135,12 +135,14 @@ For the deeper technical reference, see [`docs/ARCHITECTURE.md`](docs/ARCHITECTU ## Available applications -Templates live in [`streamspace-templates`](https://github.com/streamspace-dev/streamspace-templates). The image-build pipeline in that repo is set up to publish signed multi-arch images to `ghcr.io/streamspace-dev/` with cosign signatures and SPDX SBOM attestations. +Templates live in [`streamspace-templates`](https://github.com/streamspace-dev/streamspace-templates). The image-build pipeline in that repo publishes signed images to `ghcr.io/streamspace-dev/` with cosign keyless signatures and SPDX SBOM attestations. -> [!WARNING] -> **No image is published yet.** The pipeline's first image source — `chrome-selkies` — references a base image (`ghcr.io/selkies-project/selkies-gstreamer:24.04`) that does not exist in the upstream registry. Both the post-merge CI run and a local build attempt failed at the docker pull step. Tracked in [streamspace-templates#3](https://github.com/streamspace-dev/streamspace-templates/issues/3). The `chrome-selkies` Dockerfile needs to be rewritten `FROM ubuntu:24.04` and install Selkies from the [release tarballs](https://github.com/selkies-project/selkies/releases) before any image becomes available. -> -> The Helm chart's seeded `default-apps-configmap.yaml` and the example session above point at `ghcr.io/streamspace-dev/chrome-selkies:latest` ahead of when it actually exists; deploys will pull-fail until the build is fixed. +Currently published: + +- `ghcr.io/streamspace-dev/chrome-selkies:latest` — Google Chrome streamed via Selkies-GStreamer (linux/amd64; arm64 pending upstream Selkies binaries) + +> [!NOTE] +> The package on GHCR may be private by default. Org admin can flip it to public via [the package settings page](https://github.com/orgs/streamspace-dev/packages/container/package/chrome-selkies). Once public, anonymous pulls and the cosign verification command in [`streamspace-templates/images/README.md`](https://github.com/streamspace-dev/streamspace-templates/blob/main/images/README.md) work without auth. A Selkies-native catalog (Firefox, VS Code, full desktops, etc.) is being added on top of the same pipeline.