k0sctl icon indicating copy to clipboard operation
k0sctl copied to clipboard
verified publisher icon k0sproject

support for Chimera Linux

Open ayushnix opened this issue 8 months ago • 2 comments

I was trying to install k0s through k0sctl on Chimera Linux and I got this error:

time="10 Apr 25 17:32 IST" level=debug msg="[OpenSSH] [email protected]:22: NAME=\"Chimera\""
time="10 Apr 25 17:32 IST" level=debug msg="[OpenSSH] [email protected]:22: ID=\"chimera\""
time="10 Apr 25 17:32 IST" level=debug msg="[OpenSSH] [email protected]:22: PRETTY_NAME=\"Chimera Linux\""
time="10 Apr 25 17:32 IST" level=debug msg="[OpenSSH] [email protected]:22: HOME_URL=\"https://chimera-linux.org\""
time="10 Apr 25 17:32 IST" level=debug msg="[OpenSSH] [email protected]:22: DOCUMENTATION_URL=\"https://chimera-linux.org/docs\""
time="10 Apr 25 17:32 IST" level=debug msg="[OpenSSH] [email protected]:22: LOGO=\"chimera-logo\""
time="10 Apr 25 17:32 IST" level=debug msg="[OpenSSH] [email protected]:22: ANSI_COLOR=\"0;38;2;214;79;93\""
time="10 Apr 25 17:32 IST" level=warning msg="received an interrupt signal, aborting operation"
time="10 Apr 25 17:32 IST" level=info msg="\x1b[31m==> Apply failed\x1b[0m"
time="10 Apr 25 17:32 IST" level=fatal msg="apply failed - log file saved to /home/miller/.cache/k0sctl/k0sctl.log: failed on 1 hosts:\n - [OpenSSH] [email protected]:22: context canceled\nnot supported\nbase os detected but version resolving failed\nnot supported: invalid or incomplete os-release file contents, at least ID and VERSION_ID required"

I'm not sure why but it seems that support for each distribution needs to be added manually for k0sctl to run. Not sure if k0s has any similar limitation.

ayushnix avatar Apr 10 '25 12:04 ayushnix

I'm not sure why but it seems that support for each distribution needs to be added manually for k0sctl to run

Yes, k0sctl interacts with the file system layout, the package management system, init system and so on. This is kinda distro specific. There's the ID_LIKE key in /etc/os-release, which is used as a fallback for derivative and generally "similar" distros, so not every distro needs to be known by k0sctl, as long as there's some "popular" one that can be referenced in ID_LIKE. Chimera doesn't fall into that category, though.

You could try to write an OS module that supports Chimera. I reckon it uses apk and dinit: apk is not a problem, but dinit might be, as this is not yet supported by k0sctl/k0s at all.

Not sure if k0s has any similar limitation.

K0s provides the install, start, and stop subcommands that interact with the init system, so the dinit support would have to go there as well. On the other hand, if you're comfortable building the dinit service for k0s yourself, or just running it manually via the controller or worker subcommands, you should have no problem running k0s on Chimera. However, you will have to take care of the installation on your own.

twz123 avatar Apr 11 '25 08:04 twz123

k0sctl also has the ID_LIKE override that you could use if chimera was based on some supported distro.

apiVersion: ...
spec:
  hosts:
    - role: controller
      os: debian

but it seems chimera is a bit different from anything, it's not based on debian or other supported distros:

  • It uses musl instead of glibc
  • It uses the apk-tools package manager from Alpine, but Chimera uses it with a different repository.
  • The init system is dinit, I think this will rule out using k0s install without k0s changes

kke avatar Apr 15 '25 12:04 kke