Containerd package shouldn't provide runc which is packaged by distros already
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 35
- Forks
- 38
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 14
Description
Hi,
As a continuation of the issue in the current repository https://github.com/docker/packaging/issues/327 I think we should simply stop trying to compile/package runc here. We are in 2023, distros now all have a runc package I guess, which hopefully is well maintained. Installing containerd with runc already installed shouldn't result in the system runc package to be uninstalled (making typically a co-installation with podman fail).
Cheers,
Romain
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 linked docker/packaging issue 327 and the repository's package definitions for containerd and runc. The work is done when the containerd packages no longer compile or provide runc and can coexist with the distro-provided runc package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100