Skip to content

Conversation

@mkocher
Copy link
Member

@mkocher mkocher commented Jan 28, 2026

This enables warden stemcells to function on hosts that are using cgroups v2, which is increasingly common. This should not have any effects on other infrastructures as the stemcell kernel will continue to be booted with cgroups v1.

This enables warden stemcells to function on hosts that are using
cgroups v2, which is increasingly common. This should not have any
effects on other infrastructures as the stemcell kernel will continue to
be booted with cgroups v1.
@github-project-automation github-project-automation bot moved this from Inbox to Pending Merge | Prioritized in Foundational Infrastructure Working Group Jan 28, 2026
@Alphasite
Copy link
Contributor

I think this looks good to me. The main change is to use a cgroup v2 path instead of a v1 path when necessary?

Copy link
Member

@aramprice aramprice left a comment

Choose a reason for hiding this comment

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

This change seems reasonable for contexts where a Jammy stemcell image is be running in a containerized context.

@rkoster
Copy link
Contributor

rkoster commented Jan 28, 2026

Something similar would be needed here: https://github.com/cloudfoundry/bosh-linux-stemcell-builder/blob/ubuntu-noble/stemcell_builder/stages/bosh_monit/assets/monit-nftables.nft#L9

So the question on my mind is why is this needed on a noble host, and why only when using the warden cpi. Because noble host with docker cpi is fine, with both noble and jammy stemcells. In other words shouldn't this be fixed on the garden noble compatibility side?

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

Labels

None yet

Projects

Status: Pending Merge | Prioritized

Development

Successfully merging this pull request may close these issues.

4 participants