moby: integration: "error reading the kernel parameter" errors during CI
Noticed that these errors are showing up in our CI;
time="2019-07-13T13:01:11.226286097Z" level=error msg="error reading the kernel parameter net.ipv4.neigh.default.gc_thresh3" error="open /proc/sys/net/ipv4/neigh/default/gc_thresh3: no such file or directory"
time="2019-07-13T13:01:11.226336974Z" level=error msg="error reading the kernel parameter net.ipv4.neigh.default.gc_thresh1" error="open /proc/sys/net/ipv4/neigh/default/gc_thresh1: no such file or directory"
time="2019-07-13T13:01:11.226383933Z" level=error msg="error reading the kernel parameter net.ipv4.neigh.default.gc_thresh2" error="open /proc/sys/net/ipv4/neigh/default/gc_thresh2: no such file or directory"
time="2019-07-13T13:01:11.401028844Z" level=error msg="error reading the kernel parameter net.ipv4.vs.expire_nodest_conn" error="open /proc/sys/net/ipv4/vs/expire_nodest_conn: no such file or directory"
Error is coming from libnetwork; https://github.com/moby/moby/blob/0e162d992394d9216f590176991d33ff48ef3389/vendor/github.com/docker/libnetwork/drivers/overlay/ostweaks_linux.go#L9-L13
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 3
- Comments: 15 (7 by maintainers)
Just for the record, net.ipv4.vs namespace is only present if the ip_vs kernel module is loaded.
modprobe ip_vs
And it can also be added in a file in
/etc/modules-load.d/
to load it at boot time.modprobe ip_vs
and respectively addingip_vs
to/etc/modules-load.d/modules.conf
seem to have resolved this issue for me.@prologic đŸ‘‹ you can try the
check-config.sh
script, which could help finding things that are possibly missing; https://github.com/moby/moby/blob/master/contrib/check-config.shI am seeing this too after a patch of kernel on Centos 7.
Docker fails to start…
EDIT However. After af few restarts of the server and the docker servicer, it works again. Weird.