Conversation
Both Dockerfiles were inherited byte-for-byte from the original luminarr fork and still referenced luminarr throughout — the Go module ldflag paths, the output binary name, the cmd target, the non-root user in the scratch image, and the ENTRYPOINT. They compiled on luminarr because that repo's go.mod said github.com/luminarr/luminarr, but on prism the go build step immediately fails with "no Go files in ./cmd/luminarr". CI only surfaced this now because the docker job only fires on main-branch pushes (if: github.event_name == 'push' && ref == refs/heads/main), so the failure was hidden during every PR run and only appeared the moment the merge to main triggered the release path. Three places in Dockerfile.minimal also wrote /etc/passwd.luminarr and /etc/group.luminarr for the scratch-image non-root user — those filenames don't affect runtime but were renamed for consistency. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Same issue pilot just hit. The Build and push (minimal) step in
ci.yml was using ghcr.io/\${{ github.repository }}:latest-minimal,
which preserves the org casing and produces the invalid tag
ghcr.io/Beacon-Stack/prism:latest-minimal — GHCR strictly requires
lowercase image names. The sibling latest step escapes this by
using docker/metadata-action outputs which auto-lowercase; the
minimal step hardcodes the tag directly and misses that treatment.
Spell the repo explicitly as ghcr.io/beacon-stack/prism.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Both docker files were inherited byte-for-byte from the original luminarr fork and still referenced `luminarr` throughout — Go module ldflag paths, the output binary name, the `cmd/` target, the non-root user in the scratch image, and the ENTRYPOINT.
CI didn't catch this until now because the docker job gates on `github.event_name == 'push' && ref == refs/heads/main` — so the docker build only fires on merges to main, not on PR builds. The moment the earlier subtree PR merged and triggered the main CI run, the docker job failed with:
```
go build -o /luminarr ./cmd/luminarr
no Go files in ./cmd/luminarr
```
Test plan