Plan for cleaning up legacy images on docker.io/stellar/stellar-cli
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker
- Domain
- devops, documentation, release
Research direction
Start with builds.json and the current pipeline to determine which Docker Hub tags and digests are officially produced, then inventory docker.io/stellar/stellar-cli. Review the README for where the publication policy should be documented. Done means the legacy-image disposition, test repository, and ongoing cleanup policy are agreed and recorded.
Written by the indexing model from the issue text.
Description
What problem does your feature solve?
The docker.io/stellar/stellar-cli Docker Hub repository contains images that were published before this repo's pipeline existed. Those legacy images were not produced by the current builds.json-driven, digest-pinned pipeline, so they don't share its provenance, reproducibility, or pinning guarantees.
Leaving them in place creates a few problems:
- Users (and SEP-58 verifiers) can pull tags that look official but were not produced by the documented pipeline.
- The published tag/digest list no longer matches what
builds.jsonsays we publish, making the repo's source of truth misleading. - Ad-hoc/test pushes during pipeline development pollute the same namespace users consume from.
What would you like to see?
A plan with the following rough shape — exact details to be worked out in the issue/PR:
- Inventory every tag and digest currently on
docker.io/stellar/stellar-cliand classify each as:- produced by the current pipeline (matches an entry in
builds.json), or - legacy / not produced by the current pipeline.
- produced by the current pipeline (matches an entry in
- Remove (or otherwise retire — e.g. deprecate, hide, retag-and-archive) any images not produced by the current pipeline. Decide whether deletion is acceptable or whether we need a deprecation window first, given that downstream users and SEP-58
bldimgreferences may pin those digests. - Stop using
stellar/stellar-clias a test target. Pick a separate Docker Hub repo (e.g.stellar/stellar-cli-testor similar) for pipeline development and CI dry-runs, so the user-facing repo only ever receives pipeline-produced releases. - Document the policy in this repo's README so future maintainers don't re-pollute the production namespace.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from stellar/stellar-cli-docker
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
stellar/stellar-cli-docker#23 · 2 comments ·
All issues in stellar/stellar-cli-docker
Similar issues
-
New InternshipOpennew_internship
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
[BUG] Reports tab: "Unban" button tooltip shows raw `{{ip}}` placeholder instead of the IP addressOpenbug javascript ui
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bunkerity/bunkerweb#4001 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
PedestrianDynamics/pyFDS-Evac#476 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
adobe-fonts/source-serif#153 ·