opencontainers / opencontainers/runc
releases: add Docker image to release artefacts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
At the moment we do not provide the source code for glibc, which is a bit of a problem. It wouldn't make any sense to compile glibc ourselves, so the simplest way to fulfill the LGPL requirements is to just provide an image that contains the debian metadata for how to get the source packages for the very specific glibc version we were built against.
This would also help somewhat with binary reproducibility.
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
Review the release process and the existing release artefacts first, then determine where a Docker image containing Debian metadata for the built-against glibc version would be produced and published. Done means the image is included with releases and provides the required glibc source-package metadata while supporting binary reproducibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, docker, linux
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100