Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

regression: entrypoint is broken on cgroup v2 #2013

Closed
AkihiroSuda opened this issue Jan 20, 2021 · 3 comments · Fixed by #2014
Closed

regression: entrypoint is broken on cgroup v2 #2013

AkihiroSuda opened this issue Jan 20, 2021 · 3 comments · Fixed by #2014
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@AkihiroSuda
Copy link
Member

What happened:

fix_cgroup() change in https://github.com/kubernetes-sigs/kind/pull/1995/files broke cgroup v2

What you expected to happen:
It should work

How to reproduce it (as minimally and precisely as possible):

Minimal repro:

$ docker build -t kindest/base:latest ./images/base
$ docker run --rm --privileged kindest/base
stat: cannot read file system information for '/kind': No such file or directory
INFO: ensuring we can execute mount/umount even with userns-remap
INFO: remounting /sys read-only
INFO: making mounts shared
INFO: fix cgroup mounts for all subsystems
$ echo $?
1

Environment:

@AkihiroSuda AkihiroSuda added the kind/bug Categorizes issue or PR as related to a bug. label Jan 20, 2021
@BenTheElder
Copy link
Member

BenTheElder commented Jan 20, 2021

perhaps we should check for v1/v2 and split the code-path here?
we don't have v2 in CI and this change fixed a number of v1 platforms.

@BenTheElder
Copy link
Member

BenTheElder commented Jan 20, 2021

I'm also actually not sure if Kubernetes even has any cgroupsv2 CI at all yet, last I checked someone decided that meant we had to use fedora VMs ... which we didn't have a GCE VM image handy for. AFAIK SIG Node never sorted that out.

EDIT: which is not to say kind shouldn't be fixed, but rather that we probably also need to look at getting upstream CI as well still.

@BenTheElder BenTheElder added this to the v0.10.0 milestone Jan 20, 2021
AkihiroSuda added a commit to AkihiroSuda/kind that referenced this issue Jan 20, 2021
v2 support for `fix_cgroup()` was broken: kubernetes-sigs#2013

As CgroupNS is enabled by default on v2 hosts, we do not need to
mess around the cgroup mounts.

However, at least we need to create "/kubelet" cgroup (kubernetes-sigs#1969).

Fix kubernetes-sigs#2013

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
@AkihiroSuda
Copy link
Member Author

PR: #2014

AkihiroSuda added a commit to AkihiroSuda/kind that referenced this issue Jan 20, 2021
v2 support for `fix_cgroup()` was broken: kubernetes-sigs#2013

As CgroupNS is enabled by default on v2 hosts, we do not need to
mess around the cgroup mounts.

However, at least we need to create "/kubelet" cgroup (kubernetes-sigs#1969).

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
AkihiroSuda added a commit to AkihiroSuda/kind that referenced this issue Jan 20, 2021
v2 support for `fix_cgroup()` was broken: kubernetes-sigs#2013

As CgroupNS is enabled by default on v2 hosts, we do not need to
mess around the cgroup mounts.

However, at least we need to create "/kubelet" cgroup (kubernetes-sigs#1969).

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
maelvls pushed a commit to maelvls/kind that referenced this issue Jul 1, 2021
v2 support for `fix_cgroup()` was broken: kubernetes-sigs#2013

As CgroupNS is enabled by default on v2 hosts, we do not need to
mess around the cgroup mounts.

However, at least we need to create "/kubelet" cgroup (kubernetes-sigs#1969).

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants