Skip to content
OpenClaw Docs

Podman

Podman

Section titled “Podman”

Run the OpenClaw Gateway in a rootless Podman container, managed by your current non-root user.

The intended model is:

  • Podman runs the gateway container.
  • Your host openclaw CLI is the control plane.
  • Persistent state lives on the host under ~/.openclaw by default.
  • Day-to-day management uses openclaw --container <name> ... instead of sudo -u openclaw, podman exec, or a separate service user.

Prerequisites

Section titled “Prerequisites”
  • Podman in rootless mode
  • OpenClaw CLI installed on the host
  • Optional: systemd --user if you want Quadlet-managed auto-start
  • Optional: sudo only if you want loginctl enable-linger "$(whoami)" for boot persistence on a headless host

Quick start

Section titled “Quick start”

  1. One-time setup

    From the repo root, run ./scripts/podman/setup.sh.

  2. Start the Gateway container

    Start the container with ./scripts/run-openclaw-podman.sh launch.

  3. Run onboarding inside the container

    Run ./scripts/run-openclaw-podman.sh launch setup, then open http://127.0.0.1:18789/.

  4. Manage the running container from the host CLI

    Set OPENCLAW_CONTAINER=openclaw, then use normal openclaw commands from the host.

Setup details:

  • ./scripts/podman/setup.sh builds openclaw:local in your rootless Podman store by default, or uses OPENCLAW_IMAGE / OPENCLAW_PODMAN_IMAGE if you set one.
  • It creates ~/.openclaw/openclaw.json with gateway.mode: "local" if missing.
  • It creates ~/.openclaw/.env with OPENCLAW_GATEWAY_TOKEN if missing.
  • For manual launches, the helper reads only a small allowlist of Podman-related keys from ~/.openclaw/.env and passes explicit runtime env vars to the container; it does not hand the full env file to Podman.

Quadlet-managed setup:

Terminal window
./scripts/podman/setup.sh --quadlet

Quadlet is a Linux-only option because it depends on systemd user services.

You can also set OPENCLAW_PODMAN_QUADLET=1.

Optional build/setup env vars:

  • OPENCLAW_IMAGE or OPENCLAW_PODMAN_IMAGE — use an existing/pulled image instead of building openclaw:local
  • OPENCLAW_DOCKER_APT_PACKAGES — install extra apt packages during image build
  • OPENCLAW_EXTENSIONS — pre-install extension dependencies at build time

Container start:

Terminal window
./scripts/run-openclaw-podman.sh launch

The script starts the container as your current uid/gid with --userns=keep-id and bind-mounts your OpenClaw state into the container.

Onboarding:

Terminal window
./scripts/run-openclaw-podman.sh launch setup

Then open http://127.0.0.1:18789/ and use the token from ~/.openclaw/.env.

Host CLI default:

Terminal window
export OPENCLAW_CONTAINER=openclaw

Then commands such as these will run inside that container automatically:

Terminal window
openclaw dashboard --no-open
openclaw gateway status --deep
openclaw doctor
openclaw channels login

On macOS, Podman machine may make the browser appear non-local to the gateway. If the Control UI reports device-auth errors after launch, use the Tailscale guidance in Podman + Tailscale.

Podman + Tailscale

Section titled “Podman + Tailscale”

For HTTPS or remote browser access, follow the main Tailscale docs.

Podman-specific note:

  • Keep the Podman publish host at 127.0.0.1.
  • Prefer host-managed tailscale serve over openclaw gateway --tailscale serve.
  • On macOS, if local browser device-auth context is unreliable, use Tailscale access instead of ad hoc local tunnel workarounds.

See:

Systemd (Quadlet, optional)

Section titled “Systemd (Quadlet, optional)”

If you ran ./scripts/podman/setup.sh --quadlet, setup installs a Quadlet file at:

Terminal window
~/.config/containers/systemd/openclaw.container

Useful commands:

  • Start: systemctl --user start openclaw.service
  • Stop: systemctl --user stop openclaw.service
  • Status: systemctl --user status openclaw.service
  • Logs: journalctl --user -u openclaw.service -f

After editing the Quadlet file:

Terminal window
systemctl --user daemon-reload
systemctl --user restart openclaw.service

For boot persistence on SSH/headless hosts, enable lingering for your current user:

Terminal window
sudo loginctl enable-linger "$(whoami)"

Config, env, and storage

Section titled “Config, env, and storage”
  • Config dir: ~/.openclaw
  • Workspace dir: ~/.openclaw/workspace
  • Token file: ~/.openclaw/.env
  • Launch helper: ./scripts/run-openclaw-podman.sh

The launch script and Quadlet bind-mount host state into the container:

  • OPENCLAW_CONFIG_DIR -> /home/node/.openclaw
  • OPENCLAW_WORKSPACE_DIR -> /home/node/.openclaw/workspace

By default those are host directories, not anonymous container state, so config and workspace survive container replacement. The Podman setup also seeds gateway.controlUi.allowedOrigins for 127.0.0.1 and localhost on the published gateway port so the local dashboard works with the container’s non-loopback bind.

Useful env vars for the manual launcher:

  • OPENCLAW_PODMAN_CONTAINER — container name (openclaw by default)
  • OPENCLAW_PODMAN_IMAGE / OPENCLAW_IMAGE — image to run
  • OPENCLAW_PODMAN_GATEWAY_HOST_PORT — host port mapped to container 18789
  • OPENCLAW_PODMAN_BRIDGE_HOST_PORT — host port mapped to container 18790
  • OPENCLAW_PODMAN_PUBLISH_HOST — host interface for published ports; default is 127.0.0.1
  • OPENCLAW_GATEWAY_BIND — gateway bind mode inside the container; default is lan
  • OPENCLAW_PODMAN_USERNS — keep-id (default), auto, or host

The manual launcher reads ~/.openclaw/.env before finalizing container/image defaults, so you can persist these there.

If you use a non-default OPENCLAW_CONFIG_DIR or OPENCLAW_WORKSPACE_DIR, set the same variables for both ./scripts/podman/setup.sh and later ./scripts/run-openclaw-podman.sh launch commands. The repo-local launcher does not persist custom path overrides across shells.

Quadlet note:

  • The generated Quadlet service intentionally keeps a fixed, hardened default shape: 127.0.0.1 published ports, --bind lan inside the container, and keep-id user namespace.
  • It still reads ~/.openclaw/.env for gateway runtime env such as OPENCLAW_GATEWAY_TOKEN, but it does not consume the manual launcher’s Podman-specific override allowlist.
  • If you need custom publish ports, publish host, or other container-run flags, use the manual launcher or edit ~/.config/containers/systemd/openclaw.container directly, then reload and restart the service.

Useful commands

Section titled “Useful commands”
  • Container logs: podman logs -f openclaw
  • Stop container: podman stop openclaw
  • Remove container: podman rm -f openclaw
  • Open dashboard URL from host CLI: openclaw dashboard --no-open
  • Health/status via host CLI: openclaw gateway status --deep

Troubleshooting

Section titled “Troubleshooting”
  • Permission denied (EACCES) on config or workspace: The container runs with --userns=keep-id and --user <your uid>:<your gid> by default. Ensure the host config/workspace paths are owned by your current user.
  • Gateway start blocked (missing gateway.mode=local): Ensure ~/.openclaw/openclaw.json exists and sets gateway.mode="local". scripts/podman/setup.sh creates this if missing.
  • Container CLI commands hit the wrong target: Use openclaw --container <name> ... explicitly, or export OPENCLAW_CONTAINER=<name> in your shell.
  • openclaw update fails with --container: Expected. Rebuild/pull the image, then restart the container or the Quadlet service.
  • Quadlet service does not start: Run systemctl --user daemon-reload, then systemctl --user start openclaw.service. On headless systems you may also need sudo loginctl enable-linger "$(whoami)".
  • SELinux blocks bind mounts: Leave the default mount behavior alone; the launcher auto-adds :Z on Linux when SELinux is enforcing or permissive.
Section titled “Related”