Skip to content

fix(GH-2284): Put docker:dind in proper cgroup parent#4480

Open
marverix wants to merge 1 commit intoactions:masterfrom
cdqag:GH-2284
Open

fix(GH-2284): Put docker:dind in proper cgroup parent#4480
marverix wants to merge 1 commit intoactions:masterfrom
cdqag:GH-2284

Conversation

@marverix
Copy link
Copy Markdown

@marverix marverix commented May 4, 2026

Hello,

This PR is fix for ticket openeded since 2023: #2284 .

The idea is to use dockerd cgroup-parent flag to put dind containers in proper control groups.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR aims to address GH-2284 by configuring the Docker-in-Docker (docker:dind) daemon to place nested Docker containers under the runner Pod’s cgroup via dockerd --cgroup-parent, improving cgroupv2 resource accounting/limits behavior.

Changes:

  • Add a --cgroup-parent=... flag to the dind dockerd args.
  • Inject the Pod UID into the dind container via the Downward API (metadata.uid) for use in the cgroup parent path.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +118 to +125
- --cgroup-parent=/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod${POD_UID//-/_}.slice
env:
- name: DOCKER_GROUP_GID
value: "123"
- name: POD_UID
valueFrom:
fieldRef:
fieldPath: metadata.uid
- dockerd
- --host=unix:///var/run/docker.sock
- --group=$(DOCKER_GROUP_GID)
- --cgroup-parent=/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod${POD_UID//-/_}.slice
- dockerd
- --host=unix:///var/run/docker.sock
- --group=$(DOCKER_GROUP_GID)
- --cgroup-parent=/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod${POD_UID//-/_}.slice
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot apply changes based on this feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants