AKS sysbox container missing /proc/sys/net/ipv4/neigh/default
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Sysbox installed on AKS nodes, with image used nestybox/sysbox-deploy-k8s:latest , container running successfully. But the sysbox container missing the below mentioned path:-
[root@sysbox-deploy-k8s-bmptg /]# ls -l //proc/sys/net/ipv4/neigh/default/gc_thresh1
ls: cannot access //proc/sys/net/ipv4/neigh/default/gc_thresh1: No such file or directory
But the host on which sysbox container is running having the above mentioned path .
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
Reproduce the missing /proc/sys/net/ipv4/neigh/default/gc_thresh1 path in the reported Sysbox container on AKS, then compare it with the host path and the container runtime configuration. Determine whether the path should be exposed by Sysbox; done means the behavior is explained and, if appropriate, covered by a confirmed fix or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100