Increase inotify limit in your CI workers
Today I tripped over a CI failure that I had to think about for a while. I build zensical static sites in CI on my Forgejo instance. These builds had been working fine, then suddenly started failing with no code changes. Naturally, I assumed something upstream broke — maybe a new uv release, maybe zensical. I pinned versions. I tested older versions. Same failure every time. That ruled out regressions and pushed me toward the environment. I pulled the runner and worker images locally and built the sites just fine… But that doesn’t perfectly emulate the CI setup - my forgejo runner relies on docker -in-docker and so we aren’t just running a container on a host, we have this middle layer to consider… I wasn’t sure how to really test this out locally so I succomed to AI and here’s where Jipity got me in about 5 minutes… The failure # The builds blew up with: At first glance it means nothing to me but Jipity says this screams ulimit. So following the AI overlords I checked: was already ver…