Closed vangourd closed 1 month ago
I tried removing boot.isContainer = true;
because this is a VM, and will be bare-metal. Still didn't resolve this issue.
Ah I figured out my issue at the least.
So I forked this repo. https://github.com/vangourd/k0s-nix. Then I ran nix flake update
. Then I pointed my flake to my own github repository (probably a good idea anyway).
Then I ran sudo nix-collect-garbage -d
remove the old references. And voila it seems to be working now.
I'm curious on with the intended behavior of lock file whether or not this repo could be adapted in a way that would make it easy to reference in others flakes. However because of security I think it probably is best to audit the config yourself, then fork it. One can simply run nix flake update
on their own then.
Maybe I'm not even thinking about it appropriately with flakes being entry points as opposed to flakes all the way down.
Perhaps like referenced in https://github.com/johbo/k0s-nix/issues/5 a better way of composing the config would mean you aren't tying yourself to the package versions in this flake.
I am new to Nix and I think I'm realizing I cannot solve this on my own with my knowledge level.
I think I'm receiving the following error possible because some of the packages I'm using from this k0s flake are out of date.
Now I've tried running
nix flake update
but that's not resolving it and I've also tried. https://discourse.nixos.org/t/solved-bzimage-causes-an-error-when-running-sudo-nixos-rebuild-switch-24-05/49220Which every description I find online recommends
sudo nix-collect-garbage -d
which also does not work.If I remove the statements I have related to k0s then I get zero problems with my flake and I can rebuild without issue.
I think I have things setup correctly in my flake.nix
Here's my flake.nix