fix(compose): raise keycloak memory limit to stop OOM crash loop - #4843
Open
repudi8or wants to merge 1 commit into
Open
fix(compose): raise keycloak memory limit to stop OOM crash loop#4843repudi8or wants to merge 1 commit into
repudi8or wants to merge 1 commit into
Conversation
512m was too tight for Keycloak 26 start-dev — it was OOM-killed during the config build-and-exit step before the JVM finished booting, then restarted indefinitely (263+ restarts on llm1). Steady-state usage after boot is ~1.1GiB, so 512m/1536m both leave too little margin under real load. with a helping hand from Claude Code Signed-off-by: repudi8or <repudi8or@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
deploy.resources.limits.memory: 512mis too tight for Keycloak 26 instart-devmodeTest plan
docker compose up -d keycloak, confirmed the container starts cleanly (RestartCount=0, OOMKilled=false) and Keycloak fully initializes (master realm created, admin console listening on :8080)with a helping hand from Claude Code