Docker containers without memory limits cause host system OOM
criticalavailabilityUpdated Oct 6, 2025(via Exa)
Technologies:
How to detect:
Running Meilisearch in Docker without --memory and --memory-swap limits allows the container to consume all host system memory, leading to hard system freezes requiring forced reboots. On EC2 instances with 64GB RAM, users report complete memory exhaustion within 6 hours during indexing operations, making the entire host unresponsive.
Recommended action:
Always set Docker memory limits when running Meilisearch containers. Use --memory and --memory-swap flags with values below total system RAM (e.g., --memory='48g' --memory-swap='48g' for 64GB host). This prevents OOM conditions from crashing the host system while allowing Docker to kill only the container if limits are exceeded.