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
- 49 LFX Mentorship
- 102 LFX Mentorship: Linux Kernel
- 550 Linux Foundation Boot Camps
- 294 Cloud Engineer Boot Camp
- 118 Advanced Cloud Engineer Boot Camp
- 52 DevOps Engineer Boot Camp
- 53 Cloud Native Developer Boot Camp
- 4 Express Training Courses
- 4 Express Courses - Discussion Forum
- 1.9K Training Courses
- 18 LFC110 Class Forum
- 6 LFC131 Class Forum
- 25 LFD102 Class Forum
- 150 LFD103 Class Forum
- 17 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 596 LFD259 Class Forum
- 102 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 3 LFS203 Class Forum
- 69 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 33 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 139 LFS253 Class Forum
- 1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 92 LFS260 Class Forum
- 129 LFS261 Class Forum
- 32 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS281 Class Forum
- 220 LFW211 Class Forum
- 166 LFW212 Class Forum
- SKF100 Class Forum
- 901 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 761 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 141 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 476 Linux System Administration
- 41 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 66 Mobile Computing
- 23 Android
- 29 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 536 Off Topic
- 131 Introductions
- 216 Small Talk
- 21 Study Material
- 816 Programming and Development
- 275 Kernel Development
- 507 Software Development
- 927 Software
- 260 Applications
- 183 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 59 All In Program
- 59 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)