Kimmo Lehto
Kimmo Lehto
I think the config syntax needs some further thinking. 1. Should it be node specific or global? 🤔 Adding node specific settings becomes quite tedious if it's something you want...
The missing port error seems to be a problem in go's knownhosts package: https://github.com/golang/go/issues/53463 The kubeconfig address bug is entirely k0sctl's fault 😁 I'll see what can be done about...
Can't understand where the `warning` comes from, there's no `log.Warn` in k0s's dir cleanup 🤔 Also can't understand why this doesn't fail with all images, since removing the volume `/var/lib/k0s`...
@ncopa you had some thoughts about some cgroupv2 thing?
k0sctl doesn't do anything to handle SELinux.
I think selinux won't allow the service to start if the binary is in a non-default location, I don't know what locations it would accept on fcos. Quick googling found...
There seems to be a difference between uploadBinary and downloading the binary using curl on the host. The curl version uses: ```go return h.Execf(`install -m 0750 -o root -g root...
Hmm, different size 🤔
I think that difference should be eliminated anyway, I'll do that change asap.
> So it seems like install do help set the correct SELinux context. Then it's possible #443 already fixes this without all the `semanage` stuff?