Running KinD inside a Sysbox container no longer works after K8s v1.25.0
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Hi,
I noticed that nestybox/kindestnode has not gotten much attention in recent years. The overview on DockerHub states "expect nestybox/kindestnode to be a temporary image" and that "once the official kindest/node image picks up the patches (soon), the need for this image will disappear".
However, I am not able to get a KinD cluster running with kindest/node. Was this patch ever made? Furthermore, I've found certain versions of nestybox/kindestnode dysfunctional. The one that I have gotten working personally is v1.20.7.
Could anyone please update me with the latest on recommended practices?
Thanks.
Contributor guide
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 by reproducing the reported KinD-in-Sysbox failure with the current kindest/node image and compare it with the working nestybox/kindestnode v1.20.7 image linked in the issue. Check whether the requested patch exists and document a validated current recommendation or the remaining compatibility work.
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
- 25/100