Replies: 5 comments 1 reply
-
|
Hi @byteshiva thanks for opening this issue! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Logs Details
Details - docker logs 3cd62d8068f8
Reference: |
Beta Was this translation helpful? Give feedback.
0 replies
-
Since you reference the nixos Wiki - did you try https://nixos.wiki/wiki/K3s#Raspberry_Pi_not_working which corresponds to the fatal log of the server container? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Despite configuring the system with the appropriate kernel parameters and setting up the Nix shell as per the provided script, I'm consistently encountering connection refusal errors when attempting to connect to the server. Steps to Reproduce: Details1. Created a new Nix shell using the provided script `run.sh`. cat run.sh
export NIXPKGS_ALLOW_UNFREE=1
nix-shell -E '
let
nixpkgs = import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/nixos-unstable.tar.gz") {};
in
nixpkgs.mkShell {
buildInputs = with nixpkgs; [ k3d k3s docker containerd runc ];
shellHook = "export KUBECONFIG=kubeconfig";
}'
boot.kernelParams = [
"cgroup_enable=cpuset"
"cgroup_memory=1"
"cgroup_enable=memory"
];
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
[Converted this to a discussion]
This is solely because the server itself isn't able to start due to the cpuset cgroup error: I have no idea about nix, but probably there's some more configuration to it. According to this old thread, I'm pretty sure that it should work. |
Beta Was this translation helpful? Give feedback.
-
|
In case this helps, I saw the same message when using k3d with Jetify Devbox (wrapper around NixOS) On my host system (where k3d is installed using the official install script), when checking the k3d version I see: k3d --version
k3d version v5.7.3
k3s version v1.30.3-k3s1 (default)But inside the Devbox shell (using NixOS distributed k3d), when checking the k3d version I see: k3d --version
k3d version v5.7.4
k3s version v1.21.7-k3s1 (default)The clue was the mismatched I was able to get the NixOS version of k3d working after specifying a custom image instead of the default one in the k3d config file. # your-k3d-config.yaml
...
image: "rancher/k3s:v1.31.3-k3s1"
...
# This file is used as: k3d cluster create --config your-k3d-config.yamlA command-line alternative is to use the FYI, I got the list of all available docker images for k3s here, and then picked out the latest stable release at the time, which was |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description:
Creating a Kubernetes cluster with k3d on NixOS fails during the server node startup, leaving the cluster creation incomplete.
Steps to Reproduce:
sample.sh.Step 1 - Details
sample.sh
sample.shon a NixOS environment.Step 4: - Details
Error
k3d cluster create --api-port 6550 -p "8081:80@loadbalancer" --agents 2
Extra:
k3d cluster list --verbose --trace
Environment:
Error Message:
Workaround:
No known workaround exists currently. Users are unable to create Kubernetes clusters using k3d on NixOS until this issue is resolved.
Logs - Creating Sample Cluster on NIXOS
Beta Was this translation helpful? Give feedback.
All reactions