systemd-udevd can stop sysbox service
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Description:
systemd-udevd can stop sysbox service
Dec 14 23:32:31 k8sha-5 kernel: [292054.793913] Pid 7006(systemd-udevd) over core_pipe_limit
Dec 14 23:32:31 k8sha-5 kernel: [292054.793917] Skipping core dump
Dec 14 23:32:31 k8sha-5 kernel: [292054.793922] Pid 6744(systemd-udevd) over core_pipe_limit
Dec 14 23:32:31 k8sha-5 kernel: [292054.793925] Skipping core dump
Dec 14 23:32:31 k8sha-5 kernel: [292054.793960] Pid 6798(systemd-udevd) over core_pipe_limit
Dec 14 23:32:31 k8sha-5 kernel: [292054.793965] Skipping core dump
System Environment:
sysbox version 0.6.5
sysbox k8s in docker
@ctalledo
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
No source files or tests are named. Start by reproducing the failure with sysbox 0.6.5 running Kubernetes in Docker and inspect the systemd-udevd and kernel logs; done means identifying why systemd-udevd stops the sysbox service and preventing that failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100