opencontainers / opencontainers/runc
Start container failed when set some `net.*` sysctls
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
When enable net.ipv4.route.min_pmtu or net.ipv4.tcp_syncookies in runc config, container will start failed with open /proc/sys/net/ipv4/tcp_syncookies: no such file or directory. While net.ipv4.ip_local_port_range can be set.
I have read PR #303, didn't find any extra white/black list in this scene.
Could anyone tell me what's going on with this?
cc @mrunalp
Part of config
...
"linux": {
"sysctl": {
"kernel.shm_rmid_forced": "1",
"net.ipv4.route.min_pmtu": "1000",
"net.ipv4.tcp_syncookies": "0"
},
...
"namespaces": [
{
"type": "network"
},
...
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
The issue names no source files or tests. Start by reproducing the failure with the provided runc configuration and network namespace settings, then trace how Linux net.* sysctls are applied during container startup. Done means the supported sysctls have defined behavior and regression coverage explains the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100