Open tylerauerbeck opened 3 months ago
@tylerauerbeck you need to increase the file handler limit of the underlying Linux distro (Ubuntu) running on Colima
/etc/sysctl.conf
fs.inotify.max_user_watches = 1048576
fs.inotify.max_user_instances = 512
sudo systctl -p
or reboot the Colima VM@bayasdev How do you edit this file? I tried to connect to the vm via colima ssh but I only see the file system of my Mac. Started Colima with colima start --arch x86_64 --memory 16 --cpu 6 --kubernetes --vm-type vz -s
@bayasdev How do you edit this file?
I tried to connect to the vm via colima ssh but I only see the file system of my Mac.
Started Colima with
colima start --arch x86_64 --memory 16 --cpu 6 --kubernetes --vm-type vz -s
To connecting to the VM you need to type
colima ssh
Description
I'm attempting to run a POC locally that requires multiple kind clusters to demonstrate. The first three come up without issue, however the fourth has problems coming up. To be clear, I don't think this has anything to do with
kind
specifically, but more that I'm bringing up a number of containers that are probably a bit more resource intensive which require adjusting various settings.Specifically in my case I see the following in the logs of the fourth container
Is there a way to easily update the settings to allow for the necessary inotify params to be tuned? Is this easily done as part of a config file vs having to manually do this within the VM itself?
Version
Operating System
Output of
colima status
Reproduction Steps
Expected behaviour
Four kind clusters can come up without issue within colima
Additional context
I haven't done anything special to configure colima. This is about as clean of an install as can be as I just installed this via
homebrew