Separate tini and rootlesskit packages
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 35
- Forks
- 38
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 14
Description
These are currently built as a part of the docker-engine.
We should probably extract them into separate packages.
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
Start by reviewing the related Moby pull request 51733 and the packaging path for docker-engine. Trace how tini and rootlesskit are currently built, then define the package boundaries needed to ship them separately. Done means both components are produced as separate packages rather than as part of docker-engine.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100