Mirantis / Mirantis/cri-dockerd
CNITimeoutSec not configurable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
Scenarios
I'm deploying ai Inference service in k8s.So I need to make container to use rdma capability.
When I'm using host-device cni plugin to move eight network devices to container, I got an error message "failed (add): netplugin failed with no error message: signal: killed".
After troubleshooting,the reason is the cni process is too long, but CNITimeoutSec(default 220sec) for cri-dockerd is not enough.
So I think maybe wo should make CNITimeoutSec configurable?
fix
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 by reviewing how cri-dockerd handles the CNITimeoutSec setting and the proposed fix in PR 491. Confirm that the timeout can be configured for CNI operations rather than remaining fixed at 220 seconds, and verify the change with the project's relevant checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- devops, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100