k8s/kind doesn't work inside CI runners #637

New Issue

dboreham · 2023-11-09T03:11:07Z

dboreham commented

2023-11-09 03:11:07 +00:00

Not 100% sure what the problem is but kind doesn't start.
As seen here: https://git.vdb.to/cerc-io/stack-orchestrator/actions/runs/791

Kind says:

ERROR: failed to create cluster: could not find a log line that matches "Reached target .*Multi-User System.*|detected cgroup v1"

Then the docker logs output is:

INFO: ensuring we can execute mount/umount even with userns-remap
INFO: remounting /sys read-only
INFO: making mounts shared
INFO: detected cgroup v2
INFO: clearing and regenerating /etc/machine-id
Initializing machine ID from random generator.
INFO: faking /sys/class/dmi/id/product_name to be "kind"
INFO: faking /sys/class/dmi/id/product_uuid to be random
INFO: faking /sys/devices/virtual/dmi/id/product_uuid as well
INFO: setting iptables to detected mode: nft
INFO: detected IPv4 address: 172.18.0.2
INFO: detected IPv6 address: fc00:f853:ccd:e793::2
INFO: starting init
systemd 247.3-7+deb11u2 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
Detected virtualization docker.
Detected architecture x86-64.
Welcome to Debian GNU/Linux 11 (bullseye)!
Set hostname to <kind-control-plane>.
Failed to create /init.scope control group: Operation not supported
Failed to allocate manager object: Operation not supported
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...

Which perhaps is : https://serverfault.com/questions/1053187/systemd-fails-to-run-in-a-docker-container-when-using-cgroupv2-cgroupns-priva

Not 100% sure what the problem is but kind doesn't start. As seen here: https://git.vdb.to/cerc-io/stack-orchestrator/actions/runs/791 Kind says: ``` ERROR: failed to create cluster: could not find a log line that matches "Reached target .*Multi-User System.*|detected cgroup v1" ``` Then the docker logs output is: ``` INFO: ensuring we can execute mount/umount even with userns-remap INFO: remounting /sys read-only INFO: making mounts shared INFO: detected cgroup v2 INFO: clearing and regenerating /etc/machine-id Initializing machine ID from random generator. INFO: faking /sys/class/dmi/id/product_name to be "kind" INFO: faking /sys/class/dmi/id/product_uuid to be random INFO: faking /sys/devices/virtual/dmi/id/product_uuid as well INFO: setting iptables to detected mode: nft INFO: detected IPv4 address: 172.18.0.2 INFO: detected IPv6 address: fc00:f853:ccd:e793::2 INFO: starting init systemd 247.3-7+deb11u2 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified) Detected virtualization docker. Detected architecture x86-64. Welcome to Debian GNU/Linux 11 (bullseye)! Set hostname to <kind-control-plane>. Failed to create /init.scope control group: Operation not supported Failed to allocate manager object: Operation not supported [!!!!!!] Failed to allocate manager object. Exiting PID 1... ``` Which perhaps is : https://serverfault.com/questions/1053187/systemd-fails-to-run-in-a-docker-container-when-using-cgroupv2-cgroupns-priva

dboreham commented

2024-01-17 15:55:08 +00:00

This is fixed in-tree, but requires a runner with certain kernel properties that are not yet present in the production Gitea runners.

dboreham commented

2024-06-03 02:27:08 +00:00

Fixed without kernel config changes now.

dboreham closed this issue

2024-06-03 02:27:09 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#637