RPirruccio

[RPirruccio]

What do you want to work on?

I hit the "K8s namespace not ready" error from #552 on a Linux host already running a k3s cluster. Dug into the container and found fs.inotify.max_user_instances was maxed out at 128, containerd couldn't create its fsnotify watcher, so the RuntimeService never came up. sysctl -w fs.inotify.max_user_instances=512 on the host fixed it immediately.

I want to submit a fix that catches this before k3s starts with a warning in cluster-entrypoint.sh and a check in openshell doctor. It doesn't change any kernel params, just tells you what's wrong and how to fix it yourself.

Why this change?

The error gives you nothing to go on. Took me a couple hours to find the real cause buried in containerd logs. This would catch it before k3s even starts.

Checklist

• I wrote this request myself (not AI-generated)
• I have read CONTRIBUTING.md

[johntmyers]

/vouch

[github-actions[bot]]

@RPirruccio has been vouched by @johntmyers.

You can now submit pull requests to OpenShell. Welcome aboard.

Please read CONTRIBUTING.md before submitting.