Replies: 3 comments 1 reply
-
This is node specific setting. I think users will have to set it if they need to not impose changes when they are not needed |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sure @hellt : Totally agree: I just want to know if we can have this enhancement. Right now, I have to do it via CLI separately. But if there is a possibility to add an option to run a script which is provided as an input to clab.yml file, it would be awesome |
Beta Was this translation helpful? Give feedback.
0 replies
-
Does an input to clab make it easier than calling the script like this?
setsysctl.sh && clab deploy ...
…On Fri, 29 Oct 2021 at 15:40, Dharmesh Shah ***@***.***> wrote:
Sure @hellt <https://github.com/hellt> : Totally agree: I just want to
know if we can have this enhancement.
Right now, I have to do it via CLI separately. But if there is a
possibility to add an option to run a script which is provided as an input
to clab.yml file, it would be awesome
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#673 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLKV5K443KRAGWMPP4L7ZDUJKP6DANCNFSM5G7JMYUQ>
.
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
hellt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
it's possible that containers will set them back so we may have to keep setting them as the containers are booting
Add following file to /etc/sysctl.d/98-containerlab-inotify.conf
fs.inotify.max_user_instances = 32768
fs.inotify.max_user_watches = 524288
Then once your large cEOS nodes based topology is being deployed using containerlab, issue below cmd to increase the limits
sudo sysctl -p /etc/sysctl.d/98-containerlab-inotify.conf
fs.inotify.max_user_instances = 32768
fs.inotify.max_user_watches = 524288
Beta Was this translation helpful? Give feedback.
All reactions