Containerization with Openclaw was not an issue for me. What was an issue was the update process. The docs is so messy and the whole process was unstable.
The only thing that hold it together was that your personal files was on their own folder and ignored by git, so if git pull or some steps in between failed, you could just do a fresh install and add your personal files / workspace data again.
I hope Nanoclaw and the other similar projects have added proper steps for upgrading the container.
Title could have mentioned this relates to Openclaw/moltbot/clawdbot too. Now the post became more relevant to read when I realized what this was about.
Wow, the Qwen team is pushing out content (models + research + blogpost) at an incredible rate! Looks like omni-modals is their focus? The benchmark look intriguing but I can’t stop thinking of the hn comments about Qwen being known for benchmaxing.
Are the collection of components run in some kind of namespace? Say I run a Pies for Gitlab (which in itself had lots of components), and I run a Pies for Frpd, do they share the same space or are they isolated from each other? Am I maybe overthinking this? Perhaps its just a program manager.
> It’s so vast that Microsoft distributes it with a sophisticated GUI installer where you navigate a maze of checkboxes, hunting for which “Workloads” or “Individual Components” contain the actual compiler. Select the wrong one and you might lose hours installing something you don’t need.
I have a vague memory of stumbling upon this hell when installing the ldc compiler for dlang [1].
The only thing that hold it together was that your personal files was on their own folder and ignored by git, so if git pull or some steps in between failed, you could just do a fresh install and add your personal files / workspace data again.
I hope Nanoclaw and the other similar projects have added proper steps for upgrading the container.
reply