ZeroClaw container images with Slack support compiled in.
FROM ghcr.io/hebbian-robotics/zeroclaw-slack:v0.8.2Every published ZeroClaw image ships the lean channel bundle — Telegram,
Discord, email, webhook — without channel-slack. Configure a Slack
channel on the official image and zeroclaw channel list reports:
🚫 Slack (configured, not compiled)
Upstream's answer is "build from source with --features channel-slack",
which is a ~35-minute Rust compile of the whole workspace. This repo does
that build in CI and publishes the result, so you don't have to.
The image is the official image with one file swapped: the zeroclaw
binary is recompiled with upstream's default features plus
channel-slack— the Slack channel (Socket Mode bot)memory-postgres— the PostgreSQL long-term memory backend ([memory] backend = "postgres"+[storage.postgres.<alias>]), for deployments where the container filesystem is ephemeral
then copied into the stock ghcr.io/zeroclaw-labs/zeroclaw image. Entrypoint
(zeroclaw daemon), distroless base, dashboard assets, nonroot user, config
paths — all unchanged. Drop-in replacement.
| Tag | Meaning |
|---|---|
v0.8.2 |
Built from upstream tag v0.8.2 (pin this) |
latest |
Most recent build |
Tags mirror upstream versions; linux/amd64 only (see below for arm64).
Anywhere you'd use the official image:
docker run -d -p 42617:42617 \
-e ZEROCLAW_providers__models__anthropic__default__api_key=sk-ant-... \
-e ZEROCLAW_SLACK_BOT_TOKEN=xoxb-... \
-e ZEROCLAW_SLACK_APP_TOKEN=xapp-... \
ghcr.io/hebbian-robotics/zeroclaw-slack:v0.8.2Slack setup (Socket Mode bot, [channels.slack.<alias>] config, allowlists)
is upstream's territory — see the
ZeroClaw Slack docs.
Verify the channel is compiled in:
docker run --rm ghcr.io/hebbian-robotics/zeroclaw-slack:v0.8.2 channel listCI publishes amd64 only (an emulated arm64 Rust build takes hours). Build natively in ~10–15 minutes:
docker build -t ghcr.io/hebbian-robotics/zeroclaw-slack:v0.8.2 .- Update the tag in
Dockerfile(ARG ZEROCLAW_VERSIONand the stage-2FROMline) and in.github/workflows/build.yml(env.ZEROCLAW_VERSION). - Skim the upstream release notes — pre-1.0, config keys move between versions.
- Push; CI builds and publishes the new tag (~35 min, cached thereafter).
- Check whether upstream now ships Slack in official images — the day
docker run ghcr.io/zeroclaw-labs/zeroclaw:<tag> channel listshows Slack compiled, this repo can retire.
MIT for the build recipe in this repo. ZeroClaw itself is Apache-2.0 — the published images contain binaries compiled from unmodified upstream source.