Containerize with RAM cap — deferred to embeddings upgrade #10
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Category: Roadmap/Infra · Priority: LOW
Summary
Docker RAM-cap recommended to phase in WITH the embeddings/Ollama upgrade, not before. Premature today on a 1.8GB box where Athena is stdlib-only and costs ~0 RAM.
Why it matters
Once Ollama + nomic-embed-text run, a hard RAM cap (
docker run -m 1g --memory-swap 1g) prevents OOM-killing the host and the Hermes/Telegram gateway — a failure mode already observed on this VPS.What happens if not done
Fine today. If skipped when #6/#8 land, a model pull or fat query could OOM the host and kill dependent services.
Suggested approach
When #6 lands:
Dockerfile+docker-compose.yml, RAM-capped,oracle.db/logsbind-mounted, cron-inside via supercronic. Confirm VPS has disk for a 2–3GB image + existing 1.3GB Ollama store.