Docmost Container Update Fix
Symptom
After Dockhand auto-updates the database container, Docmost fails to start with DNS errors:
getaddrinfo ENOTFOUND db
Failed to connect to database after 15 attempts
Root Cause
Dockhand recreates containers without docker-compose, which loses the network aliases (db, redis) that Docmost needs for DNS resolution.
Quick Fix
Navigate to the Docmost directory and restart via docker-compose:
cd ~/docker/docmost
docker-compose down
docker-compose up -d
This recreates containers with proper network aliases. Data in external volumes is preserved.
Verification
Check that Docmost is running:
docker ps | grep docmost
All three containers (docmost-docmost-1, docmost-db-1, docmost-redis-1) should show as "Up" with healthy status.
Prevention
- Exclude Docmost from Dockhand monitoring, OR
- Accept occasional manual fixes after auto-updates