OpenClaw on Unraid: Docker Container Setup Guide

Key Takeaways

Official Docker image: openclaw/openclaw on Docker Hub; Unraid Community Apps template available.

Map /mnt/user/appdata/openclaw:/config for persistent config across container updates.

Default port is 8080 — map to host port in container template settings.

Use Nginx Proxy Manager Community App for SSL termination and custom domain support.

Unraid 6.12+ Docker Compose support lets you define multi-container OpenClaw stacks.

Unraid's Docker management makes deploying and updating containers trivial. If you're already running Unraid as a NAS/homelab OS, adding OpenClaw takes about 10 minutes via the Community Apps template. Here's the complete setup.

Why Unraid for OpenClaw

Unraid combines NAS functionality with Docker container management in a single OS. For homelab users, it means your OpenClaw agent runs on the same hardware as your file storage, media server, and other self-hosted apps — no dedicated server needed.

GUI container management — start, stop, update containers without the command line
Community Apps — pre-configured templates for one-click deployment
Integrated storage — easy volume mapping to Unraid's appdata share for persistent config
Auto-start — containers restart automatically after Unraid reboots

💡

Install Community Apps plugin first

The Community Apps plugin gives you access to the Unraid app store with pre-configured Docker templates. If you don't have it, go to Plugins > Install Plugin and paste the Community Apps plugin URL. Without it, you'll need to configure the container template manually.

Docker Container Setup

Via Community Apps: search for "OpenClaw" and click Install. If the template isn't in Community Apps yet, add the container manually via Docker > Add Container:

Repository: openclaw/openclaw:latest
Name: openclaw
Network Type: bridge
Port Mappings:
  Container Port: 8080
  Host Port: 8080
Volume Mappings:
  Container Path: /config
  Host Path: /mnt/user/appdata/openclaw
Environment Variables:
  (add your API keys here)

Click Apply. Unraid pulls the image and starts the container. Check the container log for any startup errors before configuring channels.

⚠

Never store API keys in the container repository path

API keys set as Docker environment variables in the Unraid UI are stored in the container template XML in /boot/config. While not directly accessible from outside, use the env file volume mapping instead of inline variables for better security hygiene. Map a .env file from your appdata volume.

Configuration & Volumes

After first start, the OpenClaw config file is created at /mnt/user/appdata/openclaw/openclaw.yaml. Edit it directly or use the Unraid terminal:

cat /mnt/user/appdata/openclaw/openclaw.yaml

Store sensitive credentials in a separate .env file in the appdata directory:

# /mnt/user/appdata/openclaw/.env
ANTHROPIC_API_KEY=sk-ant-...
TELEGRAM_BOT_TOKEN=...
SLACK_BOT_TOKEN=...

Add a volume mapping in your container template: /mnt/user/appdata/openclaw/.env:/config/.env:ro (read-only). Reference values in openclaw.yaml as ${VARIABLE_NAME}.

Networking Setup

For public webhook access, install Nginx Proxy Manager from Community Apps. Configure a proxy host pointing to your OpenClaw container's host IP and port 8080. Add an SSL certificate using the built-in Let's Encrypt integration.

Your webhook URL becomes: https://your-domain.com/webhook/

If you don't have a domain, use a tunneling service like Cloudflare Tunnel (free) to expose your local OpenClaw instance to the internet with HTTPS — no port forwarding or static IP required.

Common Mistakes

Not mapping the appdata volume before first start means the container writes config to the container's internal filesystem. When you update the container, all config is lost. Always map the volume first.

Port conflicts — port 8080 is used by many apps on Unraid (Unraid's own dashboard uses 80 and 443). Use a different host port if 8080 is taken.
Forgetting to update the image — Unraid doesn't auto-update Docker images. Check for updates in the Docker tab or use the CA Auto Update App plugin.
Using bridge networking when br0 is better — for advanced setups where OpenClaw needs its own IP on the LAN, switch to Custom br0 network type. This makes webhook URLs cleaner (use the container's IP directly).
Not checking log after startup — always check the container log after the first start. Missing environment variables or config errors are logged there and are invisible until you look.

Frequently Asked Questions

Is there an official OpenClaw Docker image?
Yes. The official image is openclaw/openclaw on Docker Hub. A Community Apps template is also available for one-click Unraid installation.

What port does OpenClaw use on Unraid?
Port 8080 by default. Map this to a host port in your Docker container template — use a different host port if 8080 is taken.

How do I persist OpenClaw config across updates?
Map a volume from your Unraid appdata share: /mnt/user/appdata/openclaw:/config. Config files in this directory survive container updates.

Can I use Unraid's built-in reverse proxy?
Yes. Install Nginx Proxy Manager from Community Apps to configure SSL termination and route traffic to your OpenClaw container.

How do I access OpenClaw logs on Unraid?
Via the Docker container log button in the Unraid UI, or run 'docker logs openclaw' in the terminal.

Does OpenClaw work with Unraid's Docker Compose support?
Yes. Unraid 6.12+ supports Docker Compose. Define your OpenClaw stack in a compose file and manage it through the Unraid UI or CLI.

A. Larsen

Homelab Engineer · aiagentsguides.com

A. Larsen runs a full Unraid homelab and covers Docker-based AI agent deployments at aiagentsguides.com.