Add validation that we don't miss "just before EOL" changes to the Go Docker infrastructure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
When https://github.com/docker-library/golang deletes an image when a version of Go goes out of support, some odd things can happen. This happened with 1.16 (found by partner team):
for Go v1.16 images, official images switched to be bullseye based starting with 1.16.7. For MSFT images, v1.16.8 (only v1.16 one) is based on buster.
When an image goes out of support and upstream deletes their infra, we should have some way to be sure that our infra is based on the last available Dockerfiles/templates, in case our auto-merge-from-upstream frequency wasn't fast enough to catch something important.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the auto-merge-from-upstream process and the Docker infrastructure that tracks docker-library/golang templates. Define how validation should detect changes just before an upstream Go version reaches end of support, and consider the work done when the last available Dockerfiles or templates are reliably checked and preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100