| Summary: | sys-cluster/k3s: add some basic kernel config dependency checks | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bjoern Michaelsen <bjoern.michaelsen> |
| Component: | Current packages | Assignee: | Zac Medico <zmedico> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | minimal kernel config check for k3s | ||
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c980ee7420ff4d06d6a524d47ca13e7c7ac4fbd2 commit c980ee7420ff4d06d6a524d47ca13e7c7ac4fbd2 Author: Bjoern Michaelsen <bjoern.michaelsen@libreoffice.org> AuthorDate: 2021-05-10 05:31:03 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2021-05-10 05:57:23 +0000 sys-cluster/k3s: add some basic kernel config dependency checks k3s depends on lots of kernel configuration and k3s/containerd arent exactly very helpful with error messages, if the kernel is missing needed features. The attached patch will provide a set of configs needed for k3s to run. The list might be incomplete, but it is a start. Steps to reproduce: 1. emerge k3s ebuild 2. start k3s on a kernel missing the listed config expected behavior: k3s runs or warns about missing kernel features. actual behavior: k3s fails in various ways (sometimes later: not able to set up network or starting containers) and provides error messages that do not directly hint at kernel configuration amiss. Closes: https://bugs.gentoo.org/788991 Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Zac Medico <zmedico@gentoo.org> sys-cluster/k3s/k3s-1.19.10-r1.ebuild | 3 ++- sys-cluster/k3s/k3s-1.20.6.ebuild | 3 ++- sys-cluster/k3s/k3s-1.21.0.ebuild | 3 ++- 3 files changed, 6 insertions(+), 3 deletions(-) Thank you! |
Created attachment 706671 [details, diff] minimal kernel config check for k3s k3s depends on lots of kernel configuration and k3s/containerd arent exactly very helpful with error messages, if the kernel is missing needed features. The attached patch will provide a set of configs needed for k3s to run. The list might be incomplete, but it is a start. Steps to reproduce: 1. emerge k3s ebuild 2. start k3s on a kernel missing the listed config expected behavior: k3s runs or warns about missing kernel features. actual behavior: k3s fails in various ways (sometimes later: not able to set up network or starting containers) and provides error messages that do not directly hint at kernel configuration amiss.