Feature: Don't prefix images with registry
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 185
- Forks
- 24
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 5
Description
Would it be possible to prevent prefixing Docker images with the found registry?
FROM rust:1.93-slim-trixie
became
FROM index.docker.io/library/rust:1.93-slim-trixie@sha256:7e6fa79cf81be23fd45d857f75f583d80cfdbb11c91fa06180fd747fda37a61d
when I would have hoped for just appending the suffix
FROM rust:1.93-slim-trixie@sha256:7e6fa79cf81be23fd45d857f75f583d80cfdbb11c91fa06180fd747fda37a61d
P.S. Would it be possible to extract the build date (i.e. if org.opencontainers.image.created has been labeled, or an equivalent of docker inspect --format='{{.Created}}' alpine)?
Then it could be shown in an inline comment like # v1.2.3 for GitHub Actions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Dockerfile FROM rewriting and GitHub Actions image updates, but no repository file or test. Start by finding the code path that changes FROM image references and resolves registries, then identify the existing test coverage. Done should avoid adding the default registry prefix while retaining the digest suffix; the build-date request may need separate scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, go
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100