hieutq/openclaw-gemini repository overview

⁠openclaw-gemini

ghcr.io/openclaw/openclaw⁠ with the Gemini CLI⁠ preinstalled, so you can authenticate OpenClaw against Gemini using Google OAuth from inside the container.

The upstream image does not ship @google/gemini-cli, so the OAuth-based Gemini login flow is unavailable there. This image is a thin layer that adds the CLI; everything else (entrypoint, user, workdir, healthcheck) is inherited unchanged from upstream.

⁠Tags

• latest — tracks ghcr.io/openclaw/openclaw:latest
• <YYYY.M.D> — pinned to the upstream OpenClaw version (e.g. 2026.4.26)

A scheduled job rebuilds and republishes daily whenever the upstream base image digest changes.

⁠Quick start

⁠1. Authenticate Gemini once (interactive)

OAuth credentials are written to ~/.gemini/ inside the container. Mount a named volume there so the tokens survive across runs:

docker run -it --rm \
  -v openclaw-gemini-home:/home/node/.gemini \
  --entrypoint gemini \
  <your-namespace>/openclaw-gemini:latest

Follow the prompt to open the URL in your browser and paste the verification code back into the terminal.

⁠2. Run OpenClaw with Gemini OAuth available

docker run -it --rm \
  -v openclaw-gemini-home:/home/node/.gemini \
  -p 127.0.0.1:8080:8080 \
  <your-namespace>/openclaw-gemini:latest

This runs the default upstream entrypoint (node openclaw.mjs gateway --allow-unconfigured) with the Gemini CLI and its stored OAuth tokens reachable on PATH.

⁠Image details

The image is labelled with openclaw.base.digest pointing at the upstream digest it was built from, plus the standard org.opencontainers.image.base.* labels.

⁠Source

Build definition and CI workflow: github.com/toquanghieu/openclaw-docker-with-gemini⁠