Mirantis / Mirantis/cri-dockerd
kubernetes v1.27 using cri-dockerd v0.3.1
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
I0413 15:00:40.876631 16395 checks.go:833] failed to detect the sandbox image for local container runtime, output: time="2023-04-13T15:00:40+08:00" level=fatal msg="getting status of runtime: failed to template data: template: tmplExecuteRawJSON:1:9: executing \"tmplExecuteRawJSON\" at <.config.sandboxImage>: map has no entry for key \"config\""
sandboxImage using from cri, kubelete remove sandboxImage flags
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at checks.go:833 and review how sandboxImage is detected when Kubernetes v1.27 uses cri-dockerd v0.3.1. Reproduce the reported runtime-status error and verify that sandbox image detection works without the kubelet sandboxImage flag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100