Mirantis / Mirantis/cri-dockerd
HAproxy static pod which run well on containerd exits on cri-dockerd
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 356
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 3
Description
I am using HAPROXY 2.6
Here is the config causing the issue
global
maxconn 100000
no strict-limits
The docker container exits on error
[ALERT] (1) : [haproxy.main()] Cannot raise FD limit to 200052, limit is 65535.
Wondering how to raise the FD limit. The systemctl service is running with
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
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 with the HAProxy 2.6 configuration and the reported FD-limit error, then trace how the limit is passed through cri-dockerd and Docker for static pods. Compare the working containerd setup with cri-dockerd; done means the shown configuration starts without the 65535 limit failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100