Files

Apple ef3473db21 snapshot: NODE1 production state 2026-02-09

Complete snapshot of /opt/microdao-daarion/ from NODE1 (144.76.224.179).
This represents the actual running production code that has diverged
significantly from the previous main branch.

Key changes from old main:
- Gateway (http_api.py): expanded from ~40KB to 164KB with full agent support
- Router: new /v1/agents/{id}/infer endpoint with vision + DeepSeek routing
- Behavior Policy: SOWA v2.2 (3-level: FULL/ACK/SILENT)
- Agent Registry: config/agent_registry.yml as single source of truth
- 13 agents configured (was 3)
- Memory service integration
- CrewAI teams and roles

Excluded from snapshot: venv/, .env, data/, backups, .tgz archives

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-02-09 08:46:46 -08:00

1.7 KiB

Raw Blame History

🐳 Docker Desktop Incident — Node2 (MacBook)

Date: 2026-01-16 Context: Investigation per INFRASTRUCTURE.md and docs/infrastructure_quick_ref.ipynb

Summary

Docker Desktop on Node2 (MacBook) does not start the daemon. docker ps returns:

Cannot connect to the Docker daemon at unix:///Users/apple/.docker/run/docker.sock

Evidence

Docker Desktop UI process exists, but daemon is down.
Backend logs show a fatal state write error:
- no space left on device while writing .../Data/log/vm/init.log
- Followed by ExitBadState and engine shutdown.
Docker VM disk image not found (Docker.raw/Docker.qcow2 missing).
~/Library/Containers/com.docker.docker/Data/vms/0/data is empty (0B).
Host disk has plenty of free space (~697GiB).

Likely Root Cause

Corrupted or missing Docker Desktop VM disk/state. The “no space left on device” is likely the VM storage layer, not host disk.

Non-destructive Checks Completed

docker ps (fails)
Logs:
- ~/Library/Containers/com.docker.docker/Data/log/host/com.docker.backend.log
- ~/Library/Containers/com.docker.docker/Data/log/vm/init.log
Search for VM disk:
- find ~/Library -name Docker.raw -o -name Docker.qcow2 → none

Next Steps (Requires Approval)

Option A — Factory Reset (recommended, destructive):

Reset Docker Desktop (deletes all containers/images/volumes)
Recreates VM disk cleanly

Option B — Full reinstall (destructive):

Remove Docker Desktop Data directory
Reinstall Docker Desktop

Impact

Node2 services depending on Docker (STT/OCR/Vector DB/etc.) are down.
Node1 architecture references Node2 for multimodal services; current state is inconsistent with docs.

1.7 KiB Raw Blame History