docs(README): warn that chrome-selkies image is not yet published#266
Merged
Conversation
The README claimed the chrome-selkies image is the "current bootstrap image". The image source exists in streamspace-templates, but the Dockerfile uses a non-existent base image and CI has failed every build since the pipeline landed (streamspace-templates#3). Add a !WARNING block to the "Available applications" section that: - States plainly that no image is published yet - Cites the broken-base-image root cause - Links to the upstream tracking issue - Notes that the Helm chart configmap + the example Session in the Quick Start point at the unpublished tag, so deploys will pull-fail until the build is fixed No code changes; this is purely truth-in-advertising.
github-actions
Bot
added
the
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The README claimed
chrome-selkiesis the current bootstrap image. It isn't published. Local build + both CI runs since streamspace-templates#2 have failed at the docker pull step because the Dockerfile usesFROM ghcr.io/selkies-project/selkies-gstreamer:24.04, which doesn't exist in the upstream registry.Tracked in streamspace-templates#3.
What changed
A
!WARNINGblock was added to the "Available applications" section of the README that:default-apps-configmap.yamland the example Session in the Quick Start point at the unpublished tag, so deploys will pull-fail until the build is fixedNo code changes — this is purely truth-in-advertising. The architecture, the pipeline shape, and the rest of the README are still correct.
Why a warning instead of a fix
Fixing the Dockerfile is real engineering work — the rewrite needs to mirror the upstream
docker-nvidia-egl-desktopDockerfile (download release tarballs, install the Python wheel, unpack web assets) and then be tested end-to-end with a working browser stream. That belongs in its own focused PR with verified local + CI testing, not the tail of this docs sweep.