This is how people can raise their max_user_instances limit if you want to. You can also use the same to raise max_user_watches if you prefer, but usually that one is so high that it's not a problem for you. The problem for me was that GitKraken registered so many instances that the default 128 limit was breached every time.
$ sysctl fs.inotify.max_user_instances
fs.inotify.max_user_instances = 128
# Write a persistent config change to the correct directory:
$ echo "fs.inotify.max_user_instances=384" | sudo tee /etc/sysctl.d/90-inotify_max_user_instances.conf
fs.inotify.max_user_instances=384
# Reload all system configs:
$ sudo sysctl --system
...
fs.inotify.max_user_instances = 384
...
$ sysctl fs.inotify.max_user_instances
fs.inotify.max_user_instances = 384
While waiting for GitKraken to fix their bug, I'm raising my limits since I am sure my computer can handle that.
This is how people can raise their
max_user_instanceslimit if you want to. You can also use the same to raisemax_user_watchesif you prefer, but usually that one is so high that it's not a problem for you. The problem for me was that GitKraken registered so many instances that the default 128 limit was breached every time.