Blog
Docker OOM During CLI Login: A DX Problem Disguised as Infrastructure
Why ERR_DOCKER_OOM during CLI login is a developer experience problem, how Compose memory caps hide churn, and how to capture exit 137 with the command that caused it.
2026-09-04 · 6 min read · AethelLayer
Exit 137 is not just an ops ticket
When auth-worker dies under a 512Mi Compose cap, platform teams see an infrastructure incident. Product teams should see a DX incident. The developer following your quickstart never finishes login, and your evaluation ends there.
Without the exact command and container name attached to the failure, support asks them to reproduce. Most will not.
Capture the command with the kill
A CLI probe that records ERR_DOCKER_OOM with compose context lets you raise memory guidance in docs and draft an issue with evidence. That is faster than arguing from a green API chart.
Taxonomy turns repeats into roadmap
Label Docker separately from OAuth and rate limits. When the same compose file OOMs twice in a week, watch rules can escalate. Patterns beat anecdotes in roadmap debates.
Keep reading
Capture the failure before they leave
Capture the failure before they leave. Book early access or talk to sales, then install @aethellayer/sdk when you are onboarded.