Skip to content

Commit 498eebe

Browse files
authored
Merge pull request #5123 from fuweid/update-bug-report-template
.github: update bug_report.md with hint and tip
2 parents bb3fcf6 + 34e8385 commit 498eebe

1 file changed

Lines changed: 37 additions & 3 deletions

File tree

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 37 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,10 +30,44 @@ Briefly describe the problem you are having in a few paragraphs.
3030
**Describe the results you expected:**
3131

3232

33-
**Output of `containerd --version`:**
33+
**What version of containerd are you using:**
3434

3535
```
36-
(paste your output here)
36+
$ containerd --version
37+
3738
```
3839

39-
**Any other relevant information:**
40+
**Any other relevant information (runC version, CRI configuration, OS/Kernel version, etc.):**
41+
42+
<!--
43+
Tips:
44+
45+
* If containerd gets stuck on something and enables debug socket, `ctr pprof goroutines`
46+
dumps the golang stack of containerd, which is helpful! If containerd runs
47+
without debug socket, `kill -SIGUSR1 $(pidof containerd)` also dumps the stack
48+
as well.
49+
50+
* If there is something about running containerd, like consuming more CPU resources,
51+
`ctr pprof` subcommands will help you to get some useful profiles. Enable debug
52+
socket makes life easier.
53+
-->
54+
55+
<details><summary><code>runc --version</code></summary><br><pre>
56+
$ runc --version
57+
58+
</pre></details>
59+
60+
<!--
61+
Show related configuration if it is related to CRI plugin.
62+
-->
63+
64+
<details><summary><code>crictl info</code></summary><br><pre>
65+
$ crictl info
66+
67+
</pre></details>
68+
69+
70+
<details><summary><code>uname -a</code></summary><br><pre>
71+
$ uname -a
72+
73+
</pre></details>

0 commit comments

Comments
 (0)