feature/OPENCLAW_IMAGE

[ozbillwang]

This is for the idea I discussed in #2178 (comment)

My way is flexible and easy.

The improvment:

• When the environment variable OPENCLAW_IMAGE in script docker-setup.sh is not set, the setup script builds the Docker image locally and runs it through docker compose.
• In docker-compose.yml, it references the same environment variable OPENCLAW_IMAGE, my understanding is, this is the right way to use this variable, it is for pre-build image.
• When the variable OPENCLAW_IMAGE is set to anything other than openclaw:local, for example, ghcr.io/clawdbot/clawdbot:main or any other valid image name, the build step is skipped. Instead, the image is pulled directly, which reduces a lot of build time.

Here is the Usage:

export OPENCLAW_IMAGE="ghcr.io/clawdbot/clawdbot:main"
./docker-setup.sh

Note:

OPENCLAW_DOCKER_APT_PACKAGES only works at build time, which doesn't help users pulling pre-built images

This issue can be resolved easily by installing the required apt packages later, but it does require a manual step.

Greptile Overview

Greptile Summary

This PR updates docker-setup.sh to support using a prebuilt Docker image via OPENCLAW_IMAGE: when the image name is the default openclaw:local it builds locally, otherwise it pulls the specified image before running the onboarding and starting services via docker compose.

This fits into the existing setup flow by keeping .env generation/upsert the same (including writing OPENCLAW_IMAGE), while changing the image acquisition step from “always build” to “build or pull depending on image name.”

Confidence Score: 4/5

• This PR is likely safe to merge, with a small risk of compose/build configuration mismatch.
• The change is localized to docker-setup.sh and is straightforward (build vs pull). Main uncertainty is whether docker-compose.yml is configured to use the pulled image without still trying to build from a local context, which would break the new flow for non-local images.
• docker-compose.yml (ensure it uses OPENCLAW_IMAGE as image and does not require build in the pull path)

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[ozbillwang]

Not sure why these jobs are always in pending status