You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered an issue running a Concourse Worker using --runtime containerd rather than the env variable CONCOURSE_RUNTIME=containerd related to cgroups.
The issue prevented runc from properly cleaning containers, leading to OCI resources being unavailable after a while (reproducing the issue required to keep the cluster running for a few days as my workload is very small). The error was indicating it was failing to get pids from /sys/fs/cgroup/garden/cgroup.procs (no such file or directory).
This issue was fixed by providing CONCOURSE_RUNTIME=containerd rather than the CLI counterpart. It seems this issue is normally fixed by #77 but that the entrypoint script doesn't use the CLI argument but the environment variable, leading to the cgroup configuration not being correct when using the CLI argument.
I'm not sure 100% the issue is this, but using the environment variable led to multiple cgroup errors disappearing.
I still had one cgroup error (failed to write subtree controllers) that I could fix using --cgroupns=host .
Best
The text was updated successfully, but these errors were encountered:
Hi,
I've encountered an issue running a Concourse Worker using --runtime containerd rather than the env variable CONCOURSE_RUNTIME=containerd related to cgroups.
The issue prevented runc from properly cleaning containers, leading to OCI resources being unavailable after a while (reproducing the issue required to keep the cluster running for a few days as my workload is very small). The error was indicating it was failing to get pids from /sys/fs/cgroup/garden/cgroup.procs (no such file or directory).
This issue was fixed by providing CONCOURSE_RUNTIME=containerd rather than the CLI counterpart. It seems this issue is normally fixed by #77 but that the entrypoint script doesn't use the CLI argument but the environment variable, leading to the cgroup configuration not being correct when using the CLI argument.
I'm not sure 100% the issue is this, but using the environment variable led to multiple cgroup errors disappearing.
I still had one cgroup error (failed to write subtree controllers) that I could fix using --cgroupns=host .
Best
The text was updated successfully, but these errors were encountered: