Installation

Symptom When executing the openclaw start or openclaw serve command, the program fails immediately and outputs the following error message: Error: listen EADDRINUSE :::3000 at Server.setupListenHandler [as _listeningListener] (node:net:1465:14) at ListenAndServe (node:net:1398:7) at ListenAndServe (net:http:1801:9) ... This indicates that the port OpenClaw is trying to bind to (default 3000) is already occupied by another process. Root Cause Analysis Port Conflict: Another service on the local computer (such as a Node.js app, Apache, Nginx, or another OpenClaw instance) is already using port 3000. Zombie Process: A previous OpenClaw process might not have terminated properly and is still holding the port. Configuration Error: The user might have set an already occupied port in the configuration file. Solution Method 1: Find and terminate the process occupying the port macOS / Linux: ...

Symptom When deploying OpenClaw using Docker, the container exits immediately after starting. Checking the logs reveals the following error: docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused: exec: /usr/local/bin/docker-entrypoint.sh: permission denied: unknown. Or: Error: ENOENT: no such file or directory, stat '/app/config/openclaw.config.js' Root Cause Analysis File Permission Issues: The ENTRYPOINT script in the Dockerfile lacks execution permissions. Incorrect Mount Paths: The configuration file is not correctly mounted to the specified path inside the container. Improper Working Directory Setup: The working directory (WORKDIR) of the container is not set correctly. Missing Environment Variables: Required environment variables are not passed in the docker run command. Solution 1. Check and Fix the Dockerfile Ensure the Dockerfile correctly sets the entry script permissions: ...