community/k3s: panic in v1.27.4+k3s1
(Moved from upstream issue, raised by different user https://github.com/k3s-io/k3s/issues/8293)
k3s 1.27.4.1-r1 fails to start with
panic: flag alsologtostderr set at github.com/k3s-io/k3s/pkg/cli/cmds/log.go:78 before being defined
goroutine 2334 [running]:
flag.(*FlagSet).Var(0xc000122150, {0x5ccebe0, 0x8964529}, {0x43de2d7, 0xf}, {0x4549454, 0x49})
flag/flag.go:1031 +0x33a
k8s.io/klog/v2.InitFlags.func1(0xc0002943f0?)
k8s.io/klog/v2@v2.90.1/klog.go:437 +0x31
flag.(*FlagSet).VisitAll(0x89618e0?, 0xc001bddf30)
flag/flag.go:458 +0x42
k8s.io/klog/v2.InitFlags(0x5d03618?)
k8s.io/klog/v2@v2.90.1/klog.go:436 +0x45
github.com/k3s-io/k3s/pkg/daemons/executor.(*Embedded).Bootstrap.func1()
github.com/k3s-io/k3s/pkg/daemons/executor/embed.go:61 +0x55
created by github.com/k3s-io/k3s/pkg/daemons/executor.(*Embedded).Bootstrap in goroutine 1
github.com/k3s-io/k3s/pkg/daemons/executor/embed.go:54 +0x8f
1.27.3.1-r2 works fine.
According to https://github.com/k3s-io/k3s/issues/8293 this isn't reproducible in upstream k3s.