You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've started getting 2021-07-29T11:33:30.7825671Z failed to watch file "/var/log/pods/default_run-tests-2xcj7_18057078-1be1-4bba-a458-55ae462508cc/run-tests/0.log": no space left on device when trying to tail some pods in hosted CI environment using kind - looks similar to #717 (comment) with the sysctl -w fs.inotify.max_user_watches=524288 thing.
Not sure how to repro this, is there a way to configure these user limits when creating the kind node maybe?
Also, not sure what's using up the watches - any advice on how to check that? I guess would need to exec a command on the node container? :/
Set kubectl context to "kind-kind"
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
standard (default) rancher.io/local-path Delete WaitForFirstConsumer false 2s
node stats: ncpu=2, ram=7121248 kB
The text was updated successfully, but these errors were encountered:
Ok - I've fixed it by running sudo sysctl -w fs.inotify.max_user_watches=524288 on the host CI machine after installing kind - I'll close this, I don't think this is something I can blame you guys for!
We've started getting
2021-07-29T11:33:30.7825671Z failed to watch file "/var/log/pods/default_run-tests-2xcj7_18057078-1be1-4bba-a458-55ae462508cc/run-tests/0.log": no space left on device
when trying to tail some pods in hosted CI environment using kind - looks similar to #717 (comment) with thesysctl -w fs.inotify.max_user_watches=524288
thing.Not sure how to repro this, is there a way to configure these user limits when creating the kind node maybe?
Also, not sure what's using up the watches - any advice on how to check that? I guess would need to exec a command on the node container? :/
Here's the versions:
kind create logs:
some more info about the kube/host machine:
The text was updated successfully, but these errors were encountered: