diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..a51c5a8
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Report an issue when building or using bpftool
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+
+Issues on this repository are used for two purposes:
+    - Track issues that have been reported on the BPF mailing list, and are known to the maintainers
+    - Report and track issues that are proper to the GitHub mirror (such as mirror-specific files or changes)
+
+Please report new bpftool bugs to the BPF mailing list first. More people will see your report there.
+
+Mailing list address: bpf@vger.kernel.org
+Mailing list subscription: http://vger.kernel.org/vger-lists.html#bpf
+Mailing list archives: https://lore.kernel.org/bpf/
+BPF reports documentation: https://docs.kernel.org/bpf/bpf_devel_QA.html#q-how-do-i-report-bugs-for-bpf-kernel-code
+
+-->
+
+- [ ] I considered whether to report to the BPF mailing list first
+
+**Environment**
+
+- bpftool version: 
+- Linux kernel version: 
+- (optionally) clang/LLVM version: 
+
+**Describe the bug**
+
+<!--
+  A clear and concise description of what the bug is.
+  Please consider providing reproducing steps, or - when an eBPF program is involved - a minimal reproducing example.
+-->