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
student@master:/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" student@master:/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) student@master:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master Ready control-plane,master 3h35m v1.23.1 student@master:/etc/containerd$
The second variant - node becomes not ready
student@master:/etc/containerd$ sudo ln --force -s config.toml.v2 config.toml student@master:/etc/containerd$ cat config.toml disabled_plugins = ["restart"] [plugins.linux] shim_debug = true [plugins.cri.containerd.runtimes.runsc] runtime_type = "io.containerd.runsc.v1" student@master:/etc/containerd$ sudo systemctl restart containerd.service student@master:/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) student@master:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master Ready control-plane,master 3h36m v1.23.1 student@master:/etc/containerd$ sleep 30 student@master:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master NotReady control-plane,master 3h37m v1.23.1 student@master:/etc/containerd$
Switch back to the first variant - all is good
student@master:/etc/containerd$ sudo ln --force -s config.toml.v1 config.toml student@master:/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" student@master:/etc/containerd$ sudo systemctl restart containerd.service student@master:/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) student@master:/etc/containerd$ k get node NAME STATUS ROLES AGE VERSION master Ready control-plane,master 3h38m v1.23.1 student@master:/etc/containerd$
When the second variant is selected:
student@master:/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 student@master:/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
- All Categories
- 60 LFX Mentorship
- 113 LFX Mentorship: Linux Kernel
- 618 Linux Foundation IT Professional Programs
- 321 Cloud Engineer IT Professional Program
- 142 Advanced Cloud Engineer IT Professional Program
- 55 DevOps Engineer IT Professional Program
- 68 Cloud Native Developer IT Professional Program
- 6 Express Training Courses
- 6 Express Courses - Discussion Forum
- 2.3K Training Courses
- 19 LFC110 Class Forum - Discontinued
- 9 LFC131 Class Forum
- 31 LFD102 Class Forum
- 175 LFD103 Class Forum
- 22 LFD121 Class Forum
- 2 LFD137 Class Forum
- 61 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 653 LFD259 Class Forum
- 108 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 4 LFD273 Class Forum
- 2 LFS145 Class Forum
- 28 LFS200 Class Forum
- 740 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 12 LFS203 Class Forum
- 92 LFS207 Class Forum
- 301 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 12 LFS244 Class Forum
- 41 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 142 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 106 LFS260 Class Forum
- 145 LFS261 Class Forum
- 39 LFS262 Class Forum
- 83 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 20 LFS267 Class Forum
- 18 LFS268 Class Forum
- 26 LFS269 Class Forum
- 204 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 249 LFW211 Class Forum
- 177 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 907 Hardware
- 220 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 210 Networking
- 102 Printers & Scanners
- 86 Storage
- 764 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 143 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 482 Linux System Administration
- 40 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 80 Network Management
- 108 System Management
- 51 Web Management
- 72 Mobile Computing
- 25 Android
- 32 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 545 Off Topic
- 132 Introductions
- 223 Small Talk
- 22 Study Material
- 831 Programming and Development
- 282 Kernel Development
- 515 Software Development
- 974 Software
- 260 Applications
- 185 Command Line
- 3 Compiling/Installing
- 119 Games
- 318 Installation
- 65 All In Program
- 65 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)