Mirantis / Mirantis/cri-dockerd
memory leaks when pods create and delete frequently
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
when running e2e test on a kubernetes cluster(v1.28.0) with cri-dockerd 0.3.4，we found cri-dockerd eats lots of memory, up to 5GB, causing the cluster to crash. does anybody has meet the same situation? or any idea to to find out the reason?
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 reproducing the reported e2e workload with Kubernetes v1.28.0, cri-dockerd 0.3.4, and frequent pod creation and deletion. Profile cri-dockerd memory while the workload runs, then narrow the leak to the responsible component and document a reproducible test or diagnostic result. Done means the cause is identified and a verified fix or next action is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- infrastructure, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100