Container on ErrorVault — Developer Error Code Dictionary

Fix clw-memory-crash: OpenClaw Memory Exhaustion Crash Resolution

Sun, 09 Aug 2026 19:56:04 +0800

Fix clw-memory-crash: OpenClaw Memory Exhaustion Crash Resolution

The clw-memory-crash error represents one of the most critical failure modes in OpenClaw deployments. When this error manifests, the OpenClaw daemon or its managed containers have encountered an unrecoverable memory state that forces an immediate process termination. Understanding the mechanics behind this crash, implementing proper resource constraints, and establishing monitoring pipelines are essential competencies for any operator managing OpenClaw workloads in production environments.

Fix clw-fs-timeout: OpenClaw Filesystem Timeout Error

Wed, 05 Aug 2026 15:08:04 +0800

1. Symptoms

The clw-fs-timeout error manifests when OpenClaw cannot complete filesystem operations within the allocated time window. This error typically surfaces during container lifecycle operations that involve reading from or writing to mounted volumes, pulling container images, or synchronizing state with the filesystem layer.

When this error occurs, you will observe output similar to the following in your terminal:

Error: clw-fs-timeout: Filesystem operation exceeded timeout threshold
Operation: volume_sync
Timeout: 30s
Elapsed: 30.004s
Container: my-app-container
Volume: /data

Additional symptoms include containers stuck in a Mounting or Initializing state, failed deployment pipelines, and intermittent connection drops when accessing mounted directories. The OpenClaw daemon logs may contain entries with the FS_TIMEOUT severity marker, indicating that kernel-level filesystem calls did not return within the expected timeframe. In severe cases, containers may enter an unrecoverable state requiring manual cleanup.

Fix docker-network-not-found: Resolve Docker Compose 'network not found' errors

Sun, 05 Jul 2026 14:34:00 +0800

The docker-network-not-found error typically occurs when Docker Compose attempts to start services that are configured to use a specific network, but that network is either not defined within the docker-compose.yml file or does not exist as an external network on the Docker host. This issue prevents containers from being created and communicating as intended, leading to a failed deployment of your multi-container application. Understanding the various ways networks are declared and managed in Docker Compose is crucial for resolving this common problem.

Fix docker-dns-resolution-failed: Docker container fails to resolve hostnames due to DNS issues

Sat, 04 Jul 2026 11:17:00 +0800

The docker-dns-resolution-failed error indicates that a Docker container is unable to resolve domain names to IP addresses, effectively preventing it from accessing external network resources like APIs, package repositories, or other services on the internet. This issue manifests as connectivity failures within the container, even if the host machine has full network access. Understanding and resolving this error is crucial for deploying functional containerized applications that rely on external communication.

Fix docker-container-already-in-use: Container name already in use by another Docker container

Fri, 03 Jul 2026 17:51:00 +0800

When working with Docker, encountering the docker-container-already-in-use error indicates a naming conflict. Docker requires that all container names within a given Docker daemon instance are unique. This error prevents you from creating or starting a new container with a name that is already assigned to an existing container, regardless of whether that existing container is currently running, stopped, or exited. Resolving this issue involves either managing the conflicting container or choosing a different name for your new container.

Fix clw-network-exhausted: Network Resources Exhausted in OpenClaw

Wed, 17 Jun 2026 19:56:04 +0800

1. Symptoms

The clw-network-exhausted error manifests when OpenClaw detects that network resources allocated to containers, services, or the runtime environment have been fully consumed. This typically occurs during high-throughput operations, concurrent service deployments, or when background processes accumulate unbounded network handles.

Shell Output Indicating This Error:

[OpenClaw Runtime Error]
Error Code: clw-network-exhausted
Message: Network resources exhausted. Unable to establish new connections.
Context: Container 'api-service-prod' attempted to bind to port 8080
Details: Available ephemeral ports: 0/65535, Active connections: 8192/8192
Timestamp: 2024-01-15T14:32:07Z
Recommendation: Increase system network limits or terminate idle connections

Additional Symptoms Include:

Fix clw-sandbox-oom: OpenClaw Sandbox Out of Memory Error

Tue, 16 Jun 2026 07:56:04 +0800

1. Symptoms

The clw-sandbox-oom error occurs when the OpenClaw sandbox environment exhausts its allocated memory quota during code execution. This error manifests through several distinguishable indicators that help developers identify the root cause quickly.

When the memory limit is breached, the sandbox container’s kernel-level Out-of-Memory killer terminates the running process. The CLI typically outputs an error message resembling the following:

Error: clw-sandbox-oom
Sandbox execution failed: process terminated due to memory exhaustion
Memory limit: 256MB
Peak usage: 312MB
Sandbox ID: sbx_a7f3k2m9

Developers may observe the process exiting with signal code 137 (128 + 9, where 9 is SIGKILL), which is a definitive indicator that the container’s OOM killer was invoked. In interactive sessions, the sandbox may become unresponsive before crashing, or execution may halt abruptly without producing expected output. Webhook-based integrations often receive a JSON payload containing the error code, memory statistics, and a timestamp of the termination event.

Fix clw-fs-oom: OpenClaw Filesystem Out of Memory Error

Tue, 16 Jun 2026 03:08:04 +0800

1. Symptoms

The clw-fs-oom error manifests when the OpenClaw workload agent cannot allocate sufficient memory to complete filesystem operations within a running container or pod. This error typically surfaces during intensive I/O operations such as log rotation, volume mounting, or bulk file transfers.

Indicators include:

The OpenClaw agent logging repeated clw-fs-oom messages to stdout or the centralized logging system
Container health checks failing unexpectedly during file-heavy operations
Application pods entering a CrashLoopBackOff state with exit code 137 (SIGKILL due to OOM)
The error appearing in the OpenClaw dashboard under workload events with the specific error code CLW-FS-OOM
Degraded performance when accessing mounted volumes or performing sequential write operations
Memory usage graphs showing a sudden spike followed by a drop to zero (process termination)

Typical shell output:

Fix clw-memory-oom: OpenClaw Out of Memory Error Resolution

Sat, 13 Jun 2026 17:32:04 +0800

1. Symptoms

The clw-memory-oom error occurs when an OpenClaw-managed workload exhausts its allocated memory resources. This error manifests through several distinct symptoms that help identify the root cause.

Primary Symptoms:

When the memory limit is reached, the OpenClaw runtime generates a specific error event:

[ERROR] clw-memory-oom: Container workload-xyz exceeded memory limit [ERROR] Current usage: 2048Mi, Limit: 2048Mi [ERROR] Memory allocation request rejected


**Observable Symptoms:**

- **Container restart loops**: The workload container enters an `OOMKilled` state and restarts repeatedly
- **Application crashes**: The process terminates unexpectedly without graceful shutdown
- **Memory metric spikes**: In monitoring dashboards, memory usage graphs show a sharp vertical line at the limit threshold
- **Health check failures**: Liveness probes fail after the container is killed
- **Pod status changes**: In Kubernetes environments, the pod status shows `OOMKilled` or `CrashLoopBackOff`

**Log Output Examples:**

```bash
# OpenClaw runtime logs
2024-01-15T10:23:45.123Z ERROR [runtime] clw-memory-oom detected
2024-01-15T10:23:45.124Z ERROR [runtime] Workload: payment-processor
2024-01-15T10:23:45.125Z ERROR [runtime] Memory stats: used=2147483648 bytes, limit=2147483648 bytes
2024-01-15T10:23:45.126Z INFO [runtime] Initiating graceful termination (timeout: 30s)
2024-01-15T10:23:45.200Z INFO [runtime] Container terminated with signal SIGKILL

# kubectl describe pod output
Name:             payment-processor
Namespace:        production
Status:           OOMKilled
Containers:
  payment-svc:
    Memory:       2148Mi / 2048Mi  # Usage exceeds limit
    Last State:   Terminated
      Reason:     OOMKilled
      Exit Code:  137

2. Root Cause

The clw-memory-oom error stems from a fundamental mismatch between memory consumption and memory allocation. Understanding the underlying causes is essential for implementing an effective solution.