Open afbjorklund opened 3 years ago
Yeah this seems like a simple fix, let's do it ASAP.
@daehyeok could you look at this?
Will let someone look at this, wasn't so simple it seems.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
This remains an issue we'd like to fix.
Currently it checks "" (empty string), if cgroup2 is false:
Since 7b0bf57f4c9b87a7b0c9362bdfbb5c0add2094d7
Most likely the code is also wrong for cgroups v2 as well ?
The end result is no memory limits, for the docker driver.
Seems to be the same issue as in #10935