Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Containerd package shouldn't provide runc which is packaged by distros already

Open
#101 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
dockerfile

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.

Description

area/pkg/containerd

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

Dominant language
Dockerfile
Stars
35
Forks
38
Avg merge
1d 18h
Merged PRs (30d)
14

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/packaging

All issues in docker/packaging

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.