1/15/2024 0 Comments Ixgbe.conf modprobe debian buster![]() ![]() Note that crio is running, so kubeadm detects crio as its container runtime. Now initialize a control-plane node by kubeadm init, with proper arguments as you want 4. We have to pass the information with –config argument. Note that, using –cgroup-driver is deprecated. Then type systemctl daemon-reload to apply the changed configurations. ![]() Nov 21 18:06:03 kubernetesdebian systemd : rvice: Failed with result 'exit-code'.įirst, add arguments to connect kubelet and cri-o by creating a file /etc/default/kubelet: KUBELET_EXTRA_ARGS=-cgroup-driver=systemd -container-runtime=remote -container-runtime-endpoint="unix:///var/run/crio/crio.sock" Nov 21 18:06:03 kubernetesdebian systemd : rvice: Main process exited, code =exited, status =255/EXCEPTION Nov 21 18:06:03 kubernetesdebian kubelet : F1121 18:06:03.006915 9249 server.go:196 ] failed to Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory Nov 21 18:06:02 kubernetesdebian systemd : Started kubelet: The Kubernetes Node Agent. Add PPA and installing packages #Īt first add a public key for Kubernetes. Installing Kubernetes in Debian is quite explained well 3. You can easily install it before installing Kubernetes, however, you can also make network configruations manually in /etc/cni/net.d.ĭon’t know details yet. Confiuring Container Networking Interface (CNI) 2 #Ĭrio suggests to install containernetworking-plugins package together, however, it will be deleted by apt when you install Kubernetes (specifically, kubernetes-cni package).Ĭontainernetworking-plugins package copies some files for CNI networking in /etc/cni/net.d, which is necessary for container networking. Nov 21 18:30:16 kubernetesdebian systemd : Started Container Runtime Interface for OCI (CRI-O ).Ĥ. Nov 21 18:30:16 kubernetesdebian systemd : Starting Container Runtime Interface for OCI (CRI-O ). Loaded: loaded (/lib/systemd/system/rvice disabled vendor preset: enabled )Īctive: active (running ) since Thu 18:30:16 KST 32min ago rvice - Container Runtime Interface for OCI (CRI-O ).Currently the latest version of in apt repository is cri-o is 1.15. $ apt-key adv -keyserver -recv-keys 8BECF1637AD8C79DĮxecuting: /tmp/apt-key-gpghome.3pmgjRnYte/gpg.1.sh -keyserver -recv-keys 8BECF1637AD8C79D You can see the following error when you type apt update after writing the source file: You can use any other Ubuntu distributions that ProjectAtomic supports. Instead, you should manually add a public key, and add apt repositories in /etc/apt/sources.list.Ĭreate a source new file /etc/apt//projectatomics.list as deb bionic main N: See apt-secure (8 ) manpage for repository creation and user configuration details. N: Updating from such a repository can 't be done securely, and is therefore disabled by default. Gpg: key 8BECF1637AD8C79D: public key "Launchpad PPA for Project Atomic" importedĮ: The repository ' focal Release' does not have a Release file. Gpg: /tmp/tmp51iyzqdm/trustdb.gpg: trustdb created Gpg: keybox '/tmp/tmp51iyzqdm/pubring.gpg' created $ add-apt-repository ppa:projectatomic/ppa -y & apt update ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |