---
title: "Discussion on \"Why Java Containers Die Silently: Fixing Docker OOM Kills\" | Hashnode"
description: "Discussion on \"Why Java Containers Die Silently: Fixing Docker OOM Kills\". Learn why Java processes inside Docker containers terminate silently with exit code 137 and how to properly configure JVM MaxRAMPercentage to prevent OOM."
url: "https://hashnode.com/posts/fixing-java-docker-oom-exit-code-137/6ab7d5341b857c605b0664b5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Java Containers Die Silently: Fixing Docker OOM Kills](https://doogal.dev/fixing-java-docker-oom-exit-code-137?utm_source=hashnode&utm_medium=feed)

Learn why Java processes inside Docker containers terminate silently with exit code 137 and how to properly configure JVM MaxRAMPercentage to prevent OOM.

Sep 26 · 5 min read · doogal.dev  
Read the article

-   [#java](https://hashnode.com/tag/java)
-   [#docker](https://hashnode.com/tag/docker)
-   [#devops](https://hashnode.com/tag/devops)
-   [#softwareengineering](https://hashnode.com/tag/softwareengineering)

## Written by

[Doogal Simpson](https://hashnode.com/@doogal)

@doogal

  
[View profile](https://hashnode.com/@doogal)

"hey doogal, what is .... ?"

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
