opencontainers / opencontainers/runc
customize cgroup doesn't work.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
I've already create a cgroup for controling my own application.
I run this func in my code for the new customize cgroup :
mount("cgp", "/var/run/cgp", "cgroup",MS_MGC_VAL, "none,name=cgp")
my customize cgroup mount success.
but when I create a new container and start it, bash got error as blow:
Error: failed to run container 576e4d: {"message":"failed to create container(XXX) on containerd: failed to create task for container(XXX): OCI runtime create failed: container_linux.go:355: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:66: mounting \\\"cgroup\\\" to rootfs \\\"rootfs\\\" at \\\"/sys/fs/cgroup\\\" caused \\\"no such file or directory\\\"\"": unknown"}
in rootfs_linux.go:984(func mountNewCgroup),I found the code does consider customize cgroup except “systemd”.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at rootfs_linux.go:984, in mountNewCgroup, and trace the cgroup mount path involved in the reported rootfs_linux.go:66 failure. Reproduce the custom cgroup setup described in the issue and document or test the expected behavior: a container should start without the reported “no such file or directory” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100