Running Manifest with containerized OpenClaw (k8s, Docker)

[SebConejo]

A user on Reddit brought up something we haven't tackled yet:

"Is there a way to run it locally when you're running OpenClaw containerized? My whole setup is k8s, and every time I look into any dashboard of any type (mission control for example) it expects to be local to OpenClaw, which doesn't work for me."

Source: https://www.reddit.com/r/openclaw/comments/1rwcvc1/comment/...
We haven't tested Manifest in a containerized setup and we don't know how it behaves in that environment right now. This is not something we want to guess on.
That said, this is the second time someone brings this up in a week. There's clearly demand for it.

If you're running OpenClaw in Docker or k8s and you've tried (or want to try) Manifest, we'd love to hear from you. What does your setup look like? What broke? What would you expect the experience to be?

Upvote this discussion if it matters to you. The more interest we see, the sooner we'll dedicate time to it.

[joryirving]

I'm the OP of that post. I've tried both dashclaw and mission control, and both expect you to run in the same space as openclaw. Obviously I could handle this with a sidecar, or just installing it inside the container and exposing more ports, but I'm wondering if there's a better way to handle it.