opencontainers / opencontainers/runc
[centos7] not ok 22 runc create exec
Open
Nobody has claimed this yet.
area/ci
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
From https://github.com/opencontainers/runc/runs/2274013221?check_suite_focus=true
not ok 22 runc create exec
# (in test file tests/integration/create.bats, line 28)
# `[ "$status" -eq 0 ]' failed
# runc spec (status=0):
#
# runc create --console-socket /tmp/bats-run-20745/runc.9tW5Ka/tty/sock test_busybox (status=1):
# time="2021-04-06T00:23:16Z" level=error msg="container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: process_linux.go:508: setting cgroup config for procHooks process caused: Unit runc-test_busybox.scope is not loaded."
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 with tests/integration/create.bats at line 28 and reproduce the runc create --console-socket failure on CentOS 7. Read the reported cgroup and systemd error in the CI output, then trace the relevant runc entry point; done means the create exec test completes successfully in the affected environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- centos, go, linux
- Domain
- cli, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100