Tools
Offline Seed
By Config-driven offline plugin and skill seeding for OpenClaw runtimes (Kubernetes, Helm, Docker).
Configuration Example
{
"plugins": [
{ "spec": "openclaw-mcp-adapter", "enabled": true }
],
"skills": [
{ "slug": "weather", "enabled": true }
]
}README
<!-- readme:hero:start -->
<p align="center">
<img src="./assets/banner.svg" alt="openclaw-offline-seed banner" />
</p>
<p align="center">
<img src="./assets/icon.svg" alt="openclaw-offline-seed premium icon" width="160" />
</p>
<p align="center">
<strong>Config-driven offline plugin and skill seeding for OpenClaw runtimes.</strong>
</p>
<p align="center">
<img src="https://img.shields.io/badge/Mode-offline_seed-0f7b3f?style=flat-square" alt="Mode Offline Seed" />
<img src="https://img.shields.io/badge/Pattern-init_container-F28C28?style=flat-square" alt="Init Container Pattern" />
<img src="https://img.shields.io/badge/Config-seed--config.json-6E40C9?style=flat-square" alt="Config File" />
<img src="https://img.shields.io/badge/Docker-ready-2496ED?logo=docker&logoColor=white&style=flat-square" alt="Docker Ready" />
<img src="https://img.shields.io/badge/Kubernetes-ready-326CE5?logo=kubernetes&logoColor=white&style=flat-square" alt="Kubernetes Ready" />
<img src="https://img.shields.io/badge/status-experimental-orange?style=flat-square" alt="Status" />
</p>
<!-- readme:hero:end -->
---
> **`openclaw-offline-seed`** is a companion image project for OpenClaw offline deployments.
>
> It builds a seed image that contains pre-installed plugins and skills, then copies them into the OpenClaw runtime home directory (`OPENCLAW_HOME_DIR`, default: `/home/node/.openclaw`) before OpenClaw starts.
This project is not tied to one chart. You can integrate it with:
- ☸️ Any Kubernetes Deployment/StatefulSet
- ⛵ Any Helm chart
- 🐳 Docker run / Docker Compose
## 📦 What gets seeded
- `extensions/*` (plugins)
- `workspace/skills/*` (skills)
## 🏠 Runtime home path
`seed-init.sh` writes into `OPENCLAW_HOME_DIR`.
- If `OPENCLAW_HOME_DIR` is not set, it defaults to `/home/node/.openclaw`.
- You can set it to any path, as long as seed and runtime use the same mounted directory.
- Keep these three values aligned:
1. `OPENCLAW_HOME_DIR` in the seed container
2. Seed container volume mount path
3. OpenClaw runtime volume mount/home path
## 🎨 Generate README header
Use the local generator (ASCII + Shields badges):
```bash
./scripts/generate-readme-hero.sh
```
To include linked GitHub badges (CI/release/license), provide your repo slug:
```bash
REPO_SLUG=owner/openclaw-offline-seed BRANCH=main CI_WORKFLOW=ci.yml ./scripts/generate-readme-hero.sh
```
## ⚙️ Configure install list
Edit [`config/seed-config.json`](./config/seed-config.json):
```json
{
"plugins": [
{ "spec": "openclaw-mcp-adapter", "enabled": true }
],
"skills": [
{ "slug": "weather", "enabled": true }
]
}
```
**Supported item formats:**
- **`plugins`**: `"<spec>"` or `{ "spec": "<spec>", "enabled": true }`
- **`skills`**: `"<slug>"` or `{ "slug": "<slug>", "enabled": true }`
> 💡 `spec` is passed directly to `openclaw plugins install`, so you can use npm specs, local paths, or tarballs.
Schema reference: [`config/seed-config.schema.json`](./config/seed-config.schema.json)
## 📁 Optional vendoring for strict offline builds
If you do not want build-time network installs, vendor local content:
- `plugins/<plugin-id>/...`
- `skills/<skill-name>/...`
Those directories are copied directly into the seed payload.
## 🏗️ Build and push
```bash
cd openclaw-offline-seed
IMAGE=REGISTRY/openclaw-offline-seed:v1 \
OPENCLAW_IMAGE=REGISTRY/openclaw:2026.2.24 \
CONFIG_PATH=config/seed-config.json \
./build.sh
docker push REGISTRY/openclaw-offline-seed:v1
```
## ⛵ Integration: Helm charts (generic)
If your chart supports overriding init containers, inject one seed init container that:
- Uses image `REGISTRY/openclaw-offline-seed:v1`
- Runs `/usr/local/bin/seed-init.sh`
- Mounts the same persistent data volume as the OpenClaw runtime at `OPENCLAW_HOME_DIR`
> ⚠️ The concrete values path differs across charts, so this project does not assume a specific chart structure.
> Use the Kubernetes snippet below as the source of truth.
## ☸️ Integration: generic Kubernetes
Use an init container that mounts the same OpenClaw data volume and runs `/usr/local/bin/seed-init.sh`.
📝 Example manifest snippet: [`examples/kubernetes-init-container.yaml`](./examples/kubernetes-init-container.yaml)
**Key points:**
- Mount the same PVC to both the seed init container and OpenClaw container
- Set `OPENCLAW_HOME_DIR` to the runtime home path you use
- Set OpenClaw plugin loading to preinstalled mode in your runtime config
## 🐳 Integration: Docker
Use a one-shot seed container against a shared named volume, then start OpenClaw with the same volume.
```bash
docker volume create openclaw-data
OPENCLAW_HOME_DIR=/home/node/.openclaw # change if your runtime uses a different home path
# 1. Run the seed container
docker run --rm \
-e OPENCLAW_HOME_DIR="$OPENCLAW_HOME_DIR" \
-v openclaw-data:"$OPENCLAW_HOME_DIR" \
REGISTRY/openclaw-offline-seed:v1
# 2. Start OpenClaw runtime
docker run -d --name openclaw \
-p 18789:18789 \
-v openclaw-data:"$OPENCLAW_HOME_DIR" \
REGISTRY/openclaw:2026.2.24 \
node dist/index.js gateway --bind lan --port 18789
```
📝 Docker Compose example: [`examples/docker-compose.yaml`](./examples/docker-compose.yaml)
## ✅ Verify runtime state
```bash
OPENCLAW_HOME_DIR=/home/node/.openclaw
# Check seeded plugins
kubectl -n <namespace> exec <openclaw-pod-or-deploy> -- sh -lc \
"ls -la ${OPENCLAW_HOME_DIR}/extensions"
# Check seeded skills
kubectl -n <namespace> exec <openclaw-pod-or-deploy> -- sh -lc \
"ls -la ${OPENCLAW_HOME_DIR}/workspace/skills"
```
## 📌 Notes
- Runtime can be fully offline when both OpenClaw and seed images are in your private registry.
- If plugin entry id in `openclaw.json` is not `openclaw-mcp-adapter`, update your config accordingly.
tools
Comments
Sign in to leave a comment