Feature Request: versioned docker images

[ForceConstant]

Would be useful to have this as a docker image that comes out with version.

[dreamwing]

Hello @ForceConstant,

Thank you for the suggestion! This is a great idea and would definitely make deployment much easier.

We are planning to implement this by:

1. Adding a Dockerfile to the repository.
2. Automating the Docker image build and push process in our CI/CD pipeline.
3. Providing versioned images (e.g., v1.x.x) and a latest tag on GitHub Container Registry (GHCR).

The implementation is currently on our roadmap. We will notify you here once the Docker image is ready!

[ForceConstant]

@dreamwing so while running as docker container, clawbridge is meant to mount the running gateway .openclaw directory in order to access logs, etc and doesn't use networking correct?

[ForceConstant]

@dreamwing Also it looks like the built image is actually private, and isn't available.

[dreamwing]

@dreamwing so while running as docker container, clawbridge is meant to mount the running gateway .openclaw directory in order to access logs, etc and doesn't use networking correct?

Hey @ForceConstant, good question!

ClawBridge actually does need networking — it serves the web dashboard on port 3000, so you'd still need -p 3000:3000.

For accessing the gateway's logs and memory files, you're on the right track — just mount the ~/.openclaw/workspace directory into the container. Something like:

docker run -d --name clawbridge \
  -p 3000:3000 \
  -e ACCESS_KEY=your_key \
  -e OPENCLAW_WORKSPACE=/openclaw/workspace \
  -v ~/.openclaw/workspace:/openclaw/workspace:ro \
  -v ./data:/app/data \
  ghcr.io/dreamwing/clawbridge:latest

We've updated the README with this example. Let me know if you run into anything!

[dreamwing]

@dreamwing Also it looks like the built image is actually private, and isn't available.

You're right — the Docker workflow was added after the last release, so no image had been published yet at that time.

We've just shipped v1.1.3 and the image is now live 🎉

docker pull ghcr.io/dreamwing/clawbridge:latest

Give it a try and let us know how it goes!

[ForceConstant]

@dreamwing interesting that you say ~/.openclaw/workspace and not just ~/.openclaw, I guess the README.md does state this only watches one agent, but that wouldn't capture any logs or sessions as they are in ~/.openclaw/agents/* right?

[dreamwing]

@dreamwing interesting that you say ~/.openclaw/workspace and not just ~/.openclaw, I guess the README.md does state this only watches one agent, but that wouldn't capture any logs or sessions as they are in ~/.openclaw/agents/* right?

@ForceConstant You're totally right! Mounting just the workspace submodule is enough for code analysis, but you'd definitely miss the live logs and session metadata since those are stored in the parent .openclaw directory.

To get the full dashboard experience in Docker, it's much better to mount the entire storage root. I've updated the README to reflect this improved recommendation:

bash

docker run -d --name clawbridge \
  -p 3000:3000 \
  -e ACCESS_KEY=your_key \
  -e OPENCLAW_STATE_DIR=/openclaw \
  -e OPENCLAW_WORKSPACE=/openclaw/workspace \
  -v ~/.openclaw:/openclaw:ro \
  -v ./data:/app/data \
  ghcr.io/dreamwing/clawbridge:latest

This way ClawBridge can "see" the whole environment while keeping it read-only for safety. Thanks for the catch!

[ForceConstant]

I haven't gotten to dig in too much, but it isn't working as docker. It is looking for some other stuff as if it was actually the openclaw host, like even calling the app openclaw for logs and such. Can you try running and see?