Repository navigation
docs: point the README at the image users can actually pull - #30
Merged
Merged
Conversation
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.
The README pointed at container images that cannot be pulled.
ghcr.io/get-coral/*is private —gh api orgs/Get-Coral/packages?package_type=containerreturns only
auroraandkapow, both marked private, and an anonymous pull isdenied for all seven modules. Meanwhile
getcoral/*on Docker Hub is public andwas last updated the same day as the most recent release.
So the published image reference now points at Docker Hub, which is also what
docs.getcoral.dev has always said.
Fathom had no Docker section at all despite a public, actively updated image.
Also replaces a link to an absolute path on the author's own machine
(
/Users/elian/Documents/code/coral/Jellyfin) with the repo it meant.