Before I Get Frustrated, Is This Really Worth My Time? #1616
Replies: 2 comments 5 replies
-
|
I can't tell you if / what problem you hit. I got originally my OpenClaw setup running, yet, well, you wrote the story. NanoClaw works very well for me, the only hiccup was Apple containers vs Docker for me (running on OS X). At the moment, I am on docker side and planning to get back to Apple container. The switch / configuration changes are comfortable for me. The only downside - and there is another thread about it - is that Claude configures it (depends on you trust to Claude) and with fork, I am not super happy to have my public repo. Yet, overall, I am happy with this project. |
Beta Was this translation helpful? Give feedback.
-
|
Here’s an alternative worth checking out: https://github.com/RikyZ90/ShibaClaw |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
OpenClaw was hyped by YouTube influencers and it didn't' deliver what they promised and came with security flaws. I've unsubscribed to all of them for wasting my time. And nemoclaw seemed better at first and then the nightmare began...
Many users are reporting that the OpenShell Sandbox networking is failing or that the Kubernetes (k3s) namespaces required for the gateway are not initializing properly. Because NemoClaw tries to wrap a complex security layer around an agent, if one part of that stack (like Docker cgroups or the K8s pod) fails, the whole "one-command" setup breaks. NemoClaw and OpenShell are essentially trying to build a high-security vault around a very "leaky" engine (OpenClaw), and right now, the vault door keeps locking the owner out.
What problems am I looking at with this codebase?
Beta Was this translation helpful? Give feedback.
All reactions