bug_report.yaml
bug_report.yaml
| Name | About | Labels | Assignees |
|---|---|---|---|
| Bug report | Create a bug report to help improve containerd | kind/bug |
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.
Please have a look on the following tips before opening the issue:
Details
* If containerd gets stuck on something and enables debug socket, `ctr pprof goroutines` dumps the golang stack of containerd, which is helpful! If containerd runs without debug socket, `kill -SIGUSR1 $(pidof containerd)` also dumps the stack as well.-
If there is something about running containerd, like consuming more CPU resources,
ctr pprofsubcommands will help you to get some useful profiles. Enable debug
socket makes life easier. -
ctrcan't be used for testing CRI configs, as it does not use CRI API.
Briefly describe the problem you are having in a few paragraphs.
runc version, CRI configuration, OS/Kernel version, etc.
Use the following commands:
$ runc --version
$ crictl info (if you use Kubernetes)
$ uname -a