chore: drop legacy Dockerfile, rename Dockerfile.goreleaser to Dockerfile#57
Merged
Conversation
…file The repo carried two Dockerfiles: - Dockerfile: a multi-stage debian-builder image that wgets the v0.4.2 release tarball and unpacks it into a distroless final stage. The approach is largely obsolete now that multi-arch images are published to ghcr.io on every release (#44), the version is pinned to a very old release, and the download URL is amd64-only. - Dockerfile.goreleaser: the four-line distroless image used by the release pipeline. Remove the legacy file and rename the goreleaser one to plain Dockerfile, updating the .goreleaser.yml references accordingly. Co-Authored-By: Claude Opus 4.7 (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
The repo carried two Dockerfiles. This PR consolidates them.
The legacy build approach is fully covered by the multi-arch images published to `ghcr.io/daichirata/gcsproxy` on every release (#44), so the standalone download-and-package Dockerfile no longer pays for itself.
`.goreleaser.yml` references updated accordingly. `goreleaser check` still passes.
Test plan
🤖 Generated with Claude Code