Add Alpine tags to go-images
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
Right now we have Debian, Mariner, and Windows images. Upstream also has Alpine. However, apparently the linux-amd64 distribution of Go doesn't work there and it has to be recompiled in-place:
(I believe the reason is that Alpine uses musl where other distros use glibc.)
It would be nice to not have to do fresh builds inside our Docker repository, so it would be nice to not do this, but if we do, we could add musl builds to our internal rolling build to avoid building Go in go-images.
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 locating the go-images tag and rolling-build definitions, then compare how Debian, Mariner, and Windows images are produced. Read the linked upstream Alpine Dockerfile and determine whether the existing build can publish Alpine tags or requires musl builds. Done means Alpine tags are supported without an unnecessary in-repository Go rebuild, or the required build change is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100