New cluster in docker

Asking for help? Comment out what you need so we can get more information to help you!

Cluster information:

Kubernetes version:1.31
Cloud being used: (put bare-metal if not on a public cloud) bare-metal (docker really)
Installation method: kubeadm//https://www.linuxtechi.com/install-kubernetes-cluster-on-debian/
Host OS: debian 12.6//KERNEL_VERSION: 6.1.0-23-amd64
CNI and version: none yet
CRI and version: containerd GitHub - containerd/containerd: An open and reliable container runtime 1.6.20~ds1 1.6.20~ds1-1+b1

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.

no yaml yet in my config, the output i get is the following:

Blockquote
kubeadm init --ignore-preflight-errors=Swap --ignore-preflight-errors=SystemVerification --v=5
I0824 01:00:56,928541 137 initconfiguration,go:123] detected and using CRI socket: unix:///var/run/containerd/containerd,sock
I0824 01:00:56,928742 137 interface,go:432] Looking for default routes with IPv4 addresses
I0824 01:00:56,928758 137 interface,go:437] Default route transits interface “eth0”
I0824 01:00:56,928873 137 interface,go:209] Interface eth0 is up
I0824 01:00:56,928927 137 interface,go:257] Interface “eth0” has 1 addresses :[172,17,0,2/16],
I0824 01:00:56,929011 137 interface,go:224] Checking addr 172,17,0,2/16,
I0824 01:00:56,929025 137 interface,go:231] IP found 172,17,0,2
I0824 01:00:56,929047 137 interface,go:263] Found valid IPv4 address 172,17,0,2 for interface “eth0”,
I0824 01:00:56,929080 137 interface,go:443] Found active IP 172,17,0,2
I0824 01:00:56,929117 137 kubelet,go:195] the value of KubeletConfiguration,cgroupDriver is empty; setting it to “systemd”
I0824 01:00:56,929165 137 version,go:192] fetching Kubernetes version from URL: https://dl,k8s,io/release/stable-1,txt
[init] Using Kubernetes version: v1,31,0
[preflight] Running pre-flight checks
I0824 01:00:57,483631 137 checks,go:561] validating Kubernetes and kubeadm version
I0824 01:00:57,483699 137 checks,go:166] validating if the firewall is enabled and active
I0824 01:00:57,715070 137 checks,go:201] validating availability of port 6443
I0824 01:00:57,715687 137 checks,go:201] validating availability of port 10259
I0824 01:00:57,715806 137 checks,go:201] validating availability of port 10257
I0824 01:00:57,715919 137 checks,go:278] validating the existence of file /etc/kubernetes/manifests/kube-apiserver,yaml
I0824 01:00:57,715979 137 checks,go:278] validating the existence of file /etc/kubernetes/manifests/kube-controller-manager,yaml
I0824 01:00:57,716019 137 checks,go:278] validating the existence of file /etc/kubernetes/manifests/kube-scheduler,yaml
I0824 01:00:57,716065 137 checks,go:278] validating the existence of file /etc/kubernetes/manifests/etcd,yaml
I0824 01:00:57,716109 137 checks,go:428] validating if the connectivity type is via proxy or direct
I0824 01:00:57,716163 137 checks,go:467] validating http connectivity to first IP address in the CIDR
I0824 01:00:57,716222 137 checks,go:467] validating http connectivity to first IP address in the CIDR
I0824 01:00:57,716251 137 checks,go:102] validating the container runtime
I0824 01:00:57,717257 137 checks,go:637] validating whether swap is enabled or not
[WARNING Swap]: swap is supported for cgroup v2 only, The kubelet must be properly configured to use swap, Please refer to https://kubernetes,io/docs/concepts/architecture/nodes/#swap-memory, or disable swap on the node
I0824 01:00:57,717482 137 checks,go:368] validating the presence of executable crictl
I0824 01:00:57,717596 137 checks,go:368] validating the presence of executable conntrack
I0824 01:00:57,717679 137 checks,go:368] validating the presence of executable ip
I0824 01:00:57,717783 137 checks,go:368] validating the presence of executable iptables
I0824 01:00:57,717885 137 checks,go:368] validating the presence of executable mount
I0824 01:00:57,717998 137 checks,go:368] validating the presence of executable nsenter
I0824 01:00:57,718085 137 checks,go:368] validating the presence of executable ebtables
I0824 01:00:57,718185 137 checks,go:368] validating the presence of executable ethtool
I0824 01:00:57,718266 137 checks,go:368] validating the presence of executable socat
I0824 01:00:57,718351 137 checks,go:368] validating the presence of executable tc
I0824 01:00:57,718423 137 checks,go:368] validating the presence of executable touch
I0824 01:00:57,718507 137 checks,go:514] running all checks
[preflight] The system verification failed, Printing the output from the verification:
KERNEL_VERSION: 6,1,0-23-amd64
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
CGROUPS_PIDS: enabled
CGROUPS_HUGETLB: enabled
CGROUPS_IO: enabled
[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: “configs”, output: “modprobe: FATAL: Module configs not found in directory /lib/modules/6,1,0-23-amd64\n”, err: exit status 1
I0824 01:00:57,727131 137 checks,go:399] checking whether the given node name is valid and reachable using net,LookupHost
I0824 01:00:57,727198 137 checks,go:603] validating kubelet version
I0824 01:00:57,792039 137 checks,go:128] validating if the “kubelet” service is enabled and active
I0824 01:00:58,028108 137 checks,go:201] validating availability of port 10250
I0824 01:00:58,028269 137 checks,go:327] validating the contents of file /proc/sys/net/ipv4/ip_forward
I0824 01:00:58,028355 137 checks,go:201] validating availability of port 2379
I0824 01:00:58,028420 137 checks,go:201] validating availability of port 2380
I0824 01:00:58,028489 137 checks,go:241] validating the existence and emptiness of directory /var/lib/etcd
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action beforehand using ‘kubeadm config images pull’
I0824 01:00:58,031146 137 checks,go:832] using image pull policy: IfNotPresent
W0824 01:00:58,031808 137 checks,go:846] detected that the sandbox image “registry,k8s,io/pause:3,6” of the container runtime is inconsistent with that used by kubeadm,It is recommended to use “registry,k8s,io/pause:3,10” as the CRI sandbox image,
I0824 01:00:58,032456 137 checks,go:871] pulling: registry,k8s,io/kube-apiserver:v1,31,0
I0824 01:01:09,723355 137 checks,go:871] pulling: registry,k8s,io/kube-controller-manager:v1,31,0
I0824 01:01:19,652251 137 checks,go:871] pulling: registry,k8s,io/kube-scheduler:v1,31,0
I0824 01:01:31,453658 137 checks,go:871] pulling: registry,k8s,io/kube-proxy:v1,31,0
I0824 01:04:00,053392 137 checks,go:871] pulling: registry,k8s,io/coredns/coredns:v1,11,1
I0824 01:04:09,285975 137 checks,go:871] pulling: registry,k8s,io/pause:3,10
I0824 01:04:18,991685 137 checks,go:871] pulling: registry,k8s,io/etcd:3,5,15-0
[preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image registry,k8s,io/kube-apiserver:v1,31,0: failed to pull image registry,k8s,io/kube-apiserver:v1,31,0: failed to pull and unpack image “registry,k8s,io/kube-apiserver:v1,31,0”: failed to extract layer sha256:3d6fa0469044370439d20eaf7e0d25450e01335a93c13ba46e368d7785914c0c: failed to unmount /var/lib/containerd/tmpmounts/containerd-mount405877588: operation not permitted: failed to mount /var/lib/containerd/tmpmounts/containerd-mount405877588: operation not permitted: unknown
[ERROR ImagePull]: failed to pull image registry,k8s,io/kube-controller-manager:v1,31,0: failed to pull image registry,k8s,io/kube-controller-manager:v1,31,0: failed to pull and unpack image “registry,k8s,io/kube-controller-manager:v1,31,0”: failed to extract layer sha256:3d6fa0469044370439d20eaf7e0d25450e01335a93c13ba46e368d7785914c0c: failed to unmount /var/lib/containerd/tmpmounts/containerd-mount403886544: operation not permitted: failed to mount /var/lib/containerd/tmpmounts/containerd-mount403886544: operation not permitted: unknown
[ERROR ImagePull]: failed to pull image registry,k8s,io/kube-scheduler:v1,31,0: failed to pull image registry,k8s,io/kube-scheduler:v1,31,0: failed to pull and unpack image “registry,k8s,io/kube-scheduler:v1,31,0”: failed to extract layer sha256:3d6fa0469044370439d20eaf7e0d25450e01335a93c13ba46e368d7785914c0c: failed to unmount /var/lib/containerd/tmpmounts/containerd-mount31575303: operation not permitted: failed to mount /var/lib/containerd/tmpmounts/containerd-mount31575303: operation not permitted: unknown
[ERROR ImagePull]: failed to pull image registry,k8s,io/kube-proxy:v1,31,0: failed to pull image registry,k8s,io/kube-proxy:v1,31,0: failed to pull and unpack image “registry,k8s,io/kube-proxy:v1,31,0”: failed to extract layer sha256:a491099c44635c4e3706041be38b260c93c386f2bcc824e52d2b8da750907192: failed to unmount /var/lib/containerd/tmpmounts/containerd-mount2041919296: operation not permitted: failed to mount /var/lib/containerd/tmpmounts/containerd-mount2041919296: operation not permitted: unknown
[ERROR ImagePull]: failed to pull image registry,k8s,io/coredns/coredns:v1,11,1: failed to pull image registry,k8s,io/coredns/coredns:v1,11,1: failed to pull and unpack image “registry,k8s,io/coredns/coredns:v1,11,1”: failed to extract layer sha256:e023e0e48e6e29e90e519f4dd356d058ff2bffbd16e28b802f3b8f93aa4ccb17: failed to unmount /var/lib/containerd/tmpmounts/containerd-mount1030403086: operation not permitted: failed to mount /var/lib/containerd/tmpmounts/containerd-mount1030403086: operation not permitted: unknown
[ERROR ImagePull]: failed to pull image registry,k8s,io/pause:3,10: failed to pull image registry,k8s,io/pause:3,10: failed to pull and unpack image “registry,k8s,io/pause:3,10”: failed to extract layer sha256:d8bdedd33a4e22f5cb6ca641a7ada5f9e6a92ad001589480818a136184c7ce34: failed to unmount /var/lib/containerd/tmpmounts/containerd-mount130201287: operation not permitted: failed to mount /var/lib/containerd/tmpmounts/containerd-mount130201287: operation not permitted: unknown
[ERROR ImagePull]: failed to pull image registry,k8s,io/etcd:3,5,15-0: failed to pull image registry,k8s,io/etcd:3,5,15-0: failed to pull and unpack image “registry,k8s,io/etcd:3,5,15-0”: failed to extract layer sha256:f144bb4c7c7f0d2aa7eeffd36d934ec40db1ee167be727e326aad9fdc616f475: failed to unmount /var/lib/containerd/tmpmounts/containerd-mount2093519801: operation not permitted: failed to mount /var/lib/containerd/tmpmounts/containerd-mount2093519801: operation not permitted: unknown
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=,,,
error execution phase preflight
k8s,io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow,(*Runner),Run,func1
k8s,io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner,go:260
k8s,io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow,(*Runner),visitAll
k8s,io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner,go:446
k8s,io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow,(*Runner),Run
k8s,io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner,go:232
k8s,io/kubernetes/cmd/kubeadm/app/cmd,newCmdInit,func1
k8s,io/kubernetes/cmd/kubeadm/app/cmd/init,go:128
github,com/spf13/cobra,(*Command),execute
github,com/spf13/cobra@v1,8,1/command,go:985
github,com/spf13/cobra,(*Command),ExecuteC
github,com/spf13/cobra@v1,8,1/command,go:1117
github,com/spf13/cobra,(*Command),Execute
github,com/spf13/cobra@v1,8,1/command,go:1041
k8s,io/kubernetes/cmd/kubeadm/app,Run
k8s,io/kubernetes/cmd/kubeadm/app/kubeadm,go:47
main,main
k8s,io/kubernetes/cmd/kubeadm/kubeadm,go:25
runtime,main
runtime/proc,go:271
runtime,goexit
runtime/asm_amd64,s:1695