| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|
|
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|