-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubernetes v1.27 using cri-dockerd v0.3.1 #178
Comments
("pod-infra-container-image", "will be removed in 1.27. Image garbage collector will get sandbox image information from container runtimes") same in 1.27 remove this flags ? kubeadm init detect the sandbox image failed in cri-dockerd cri. |
Right, "config" is only implemented in containerd. The other runtimes only do "status", for their sudo crictl -r unix:///var/run/cri-dockerd.sock info {
"status": {
"conditions": [
{
"type": "RuntimeReady",
"status": true,
"reason": "",
"message": ""
},
{
"type": "NetworkReady",
"status": false,
"reason": "NetworkPluginNotReady",
"message": "docker: network plugin is not ready: cni config uninitialized"
}
]
}
} sudo crictl -r unix:///run/crio/crio.sock info {
"status": {
"conditions": [
{
"type": "RuntimeReady",
"status": true,
"reason": "",
"message": ""
},
{
"type": "NetworkReady",
"status": false,
"reason": "NetworkPluginNotReady",
"message": "Network plugin returns error: No CNI configuration file in /etc/cni/net.d/. Has your network provider started?"
}
]
}
} As far as I know, the output is only advisory anyway ? It shows if you forgot to configure your container runtime... |
|
The flag is still there for 1.28, and the help text now says "in a future release" (without specifying which) |
sandboxImage using from cri, kubelete remove sandboxImage flags
The text was updated successfully, but these errors were encountered: