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

CONCOURSE_RUNTIME=containerd is not the same as --runtime containerd #84

Open
alanzanattadev opened this issue Aug 15, 2022 · 0 comments

Comments

@alanzanattadev
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant