Lab 3.6 - node is not ready once /etc/containerd/config.toml is changed the second time
The instructions in containerd-setup.txt tells first to set /etc/containerd/config.toml
to
version = 2 #disabled_plugins = ["cri"] [plugins."io.containerd.runtime.v1.linux"] shim_debug = true [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc] runtime_type = "io.containerd.runc.v2" [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runsc] runtime_type = "io.containerd.runsc.v1"
And then later on to
disabled_plugins = ["restart"] [plugins.linux] shim_debug = true [plugins.cri.containerd.runtimes.runsc] runtime_type = "io.containerd.runsc.v1"
My problem is that the node becomes not ready with the second version.
Please, observe:
The first variant - all is good
[email protected]:/etc/containerd$ cat config.toml version = 2 #disabled_plugins = ["cri"] [plugins."io.containerd.runtime.v1.linux"] shim_debug = true [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc] runtime_type = "io.containerd.runc.v2" [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runsc] runtime_type = "io.containerd.runsc.v1" [email protected]:/etc/containerd$ systemctl status containerd.service | head -5 ● containerd.service - containerd container runtime Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-12-18 20:35:41 UTC; 54min ago Docs: https://containerd.io Process: 145675 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS) [email protected]:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master Ready control-plane,master 3h35m v1.23.1 [email protected]:/etc/containerd$
The second variant - node becomes not ready
[email protected]:/etc/containerd$ sudo ln --force -s config.toml.v2 config.toml [email protected]:/etc/containerd$ cat config.toml disabled_plugins = ["restart"] [plugins.linux] shim_debug = true [plugins.cri.containerd.runtimes.runsc] runtime_type = "io.containerd.runsc.v1" [email protected]:/etc/containerd$ sudo systemctl restart containerd.service [email protected]:/etc/containerd$ systemctl status containerd.service | head -5 ● containerd.service - containerd container runtime Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-12-18 21:31:11 UTC; 4s ago Docs: https://containerd.io Process: 176547 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS) [email protected]:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master Ready control-plane,master 3h36m v1.23.1 [email protected]:/etc/containerd$ sleep 30 [email protected]:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master NotReady control-plane,master 3h37m v1.23.1 [email protected]:/etc/containerd$
Switch back to the first variant - all is good
[email protected]:/etc/containerd$ sudo ln --force -s config.toml.v1 config.toml [email protected]:/etc/containerd$ cat config.toml version = 2 #disabled_plugins = ["cri"] [plugins."io.containerd.runtime.v1.linux"] shim_debug = true [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc] runtime_type = "io.containerd.runc.v2" [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runsc] runtime_type = "io.containerd.runsc.v1" [email protected]:/etc/containerd$ sudo systemctl restart containerd.service [email protected]:/etc/containerd$ systemctl status containerd.service | head -5 ● containerd.service - containerd container runtime Loaded: loaded (/lib/systemd/system/containerd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-12-18 21:33:03 UTC; 4s ago Docs: https://containerd.io Process: 176798 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS) [email protected]:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master Ready control-plane,master 3h38m v1.23.1 [email protected]:/etc/containerd$
When the second variant is selected:
[email protected]:/etc/containerd$ k describe node | tail -5 Normal NodeHasSufficientPID 3m22s kubelet Node master status is now: NodeHasSufficientPID Normal NodeAllocatableEnforced 3m21s kubelet Updated Node Allocatable limit across pods Normal NodeReady 3m21s kubelet Node master status is now: NodeReady Normal NodeNotReady 59s (x2 over 3m22s) kubelet Node master status is now: NodeNotReady Warning ContainerGCFailed 22s (x2 over 82s) kubelet rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService [email protected]:/etc/containerd$
Your help is greatly appreciated.
Answers
-
Hi @mark.kharitonov,
I would recommend continuing the lab with the config.toml that allows the node to become ready.
Regards,
-Chris0 -
I guess I have no other choice, but I would like to understand what is wrong. After all, these are the instructions. I hope this will not impede me from doing the lab.
0 -
Hi @mark.kharitonov,
Yes, I got the same issue.
May any one help to explain more detail about this and how to fix this issue?Thank you.
0 -
Hi @dennis6,
Please use the config.toml configuration that brings the node to a ready state, as suggested above.
Regards,
-Chris0
Categories
- 9.9K All Categories
- 29 LFX Mentorship
- 82 LFX Mentorship: Linux Kernel
- 465 Linux Foundation Boot Camps
- 266 Cloud Engineer Boot Camp
- 94 Advanced Cloud Engineer Boot Camp
- 43 DevOps Engineer Boot Camp
- 29 Cloud Native Developer Boot Camp
- 1 Express Training Courses
- 1 Express Courses - Discussion Forum
- 1.6K Training Courses
- 18 LFC110 Class Forum
- 4 LFC131 Class Forum
- 19 LFD102 Class Forum
- 133 LFD103 Class Forum
- 9 LFD121 Class Forum
- 60 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 544 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 20 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 36 LFS207 Class Forum
- 295 LFS211 Class Forum
- 53 LFS216 Class Forum
- 45 LFS241 Class Forum
- 39 LFS242 Class Forum
- 33 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 964 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 85 LFS260 Class Forum
- 124 LFS261 Class Forum
- 29 LFS262 Class Forum
- 78 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 16 LFS268 Class Forum
- 14 LFS269 Class Forum
- 194 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 206 LFW211 Class Forum
- 148 LFW212 Class Forum
- 890 Hardware
- 212 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 206 Networking
- 99 Printers & Scanners
- 85 Storage
- 747 Linux Distributions
- 88 Debian
- 64 Fedora
- 13 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 354 Ubuntu
- 468 Linux System Administration
- 38 Cloud Computing
- 67 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 77 Network Management
- 107 System Management
- 48 Web Management
- 62 Mobile Computing
- 22 Android
- 26 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 525 Off Topic
- 127 Introductions
- 211 Small Talk
- 19 Study Material
- 782 Programming and Development
- 256 Kernel Development
- 492 Software Development
- 919 Software
- 255 Applications
- 181 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 46 All In Program
- 46 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)