Summary

Docker builds from main can ship with incomplete runtime dependencies for the bundled memory-lancedb extension, causing memory plugin failures in container deployments.

Steps to reproduce

1. Build image from main:

   docker build -t openclaw:main-test .

2. Verify extension-required runtime dependencies:

   docker run --rm openclaw:main-test node -e "import('openai').then(()=>console.log('openai:ok')).catch(e=>console.error('openai:fail:'+e.message))"
   docker run --rm openclaw:main-test node -e "import('@lancedb/lancedb').then(()=>console.log('lancedb:ok')).catch(e=>console.error('lancedb:fail:'+e.message))"

3. Enable memory-lancedb and trigger a memory operation with OpenAI embeddings.

Expected behavior

Docker runtime should include all dependencies required by memory-lancedb, so the plugin initializes and runs consistently.

Actual behavior

Dependency availability is inconsistent in Docker runtime (for example, openai missing), so memory-lancedb fails at initialization or embedding calls.

OpenClaw version

main (tested 2026-02-17)

Operating system

Docker on Linux

Install method

docker

Logs, screenshots, and evidence

openai:fail:Cannot find package 'openai' imported from /app/[eval]
lancedb:ok

Impact and severity

Affected: Docker users of memory-lancedb
Severity: High
Frequency: Deterministic under current Docker install flow
Consequence: Memory plugin is unreliable in container deployments

Additional information

Root-cause direction: Docker build/install flow does not reliably install extension runtime dependencies.