-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AKS sysbox container missing /proc/sys/net/ipv4/neigh/default #778
Comments
Thanks for filling this one up @tanwar57. For security purposes, we are not exposing all node's |
@rodnymolina actually i was building an node application inside the docker container which is running over sysbox as runtime , SO,could you please let me how can i enable this dir or mount under sysbox container, or any other good way |
@rodnymolina any update on this ? |
Hi @tanwar57, Sorry, just replied to your question in issue #618 where you had asked this same question. Let's use this new issue though, since more specific to your problem. Copying my reply from issue #618:
Got it; so it's clear the problem is that the @rodnymolina: any idea on how can this occur? I see that sysbox-fs has a handler to emulate that directory inside Sysbox containers. As a point of comparison, on a GKE K8s cluster, using the "ubuntu with containerd" nodes, and deploying a sysbox pod with image ubu-focal-systemd-docker, I can't reproduce:
The Sysbox image won't make a different I think; it has got to be a bug in Sysbox I think. |
In my first comment above, I mentioned that not all At first glance, I thought that problem could have been caused by this specific Linux kernel not exposing the @tanwar57, please confirm the above by doing this in your host system:
Then repeat the above instructions within a sysbox container. If all looks good, then I would suggest enabling sysbox-fs debugging traces and collecting the logs that you see while executing the same instructions above. See some basic documentation here on how to do the above (just need to add |
Hello @rodnymolina please have a look / # ls -l /proc/sys/net/ipv4/neigh
/ # ls -l /proc/sys/net/ipv4/neigh/default
/ # ls -l /proc/sys/net/ipv4/neigh/default/gc_thresh1
And If I ran same thing to the sysbox container the output will be:- [root@sysbox-deploy-k8s-wrgjz /]# ls -l /proc/sys/net/ipv4/neigh
[root@sysbox-deploy-k8s-wrgjz /]# ls -l /proc/sys/net/ipv4/neigh/default
[root@sysbox-deploy-k8s-wrgjz /]# ls -l /proc/sys/net/ipv4/neigh/default/gc_thresh1
|
@rodnymolina ^^ any update on this please ? |
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:-But the host on which sysbox container is running having the above mentioned path .
The text was updated successfully, but these errors were encountered: