必应池
Home / browser-issues / Docker Container Exits Immediately with Exit Code 137 - Fix ERR_NAME_NOT_RESOLVED in Chrome-How to Find and Fix Node.js Memory Leaks

Docker Container Exits Immediately with Exit Code 137 - Fix ERR_NAME_NOT_RESOLVED in Chrome-How to Find and Fix Node.js Memory Leaks

Updated 2026-07-28 11:05:51browser-issues
Docker Container Exits Immediately with Exit Code 137 - Fix ERR_NAME_NOT_RESOLVED in Chrome-How to Find and Fix Node.js Memory Leaks
Likely symptom
Likely cause
Safe rollback

Verification route

  • Repeat the original action, not only a simplified test case.
  • Restart the app or reload the service after configuration changes.