Keycloak DevServices Container Getting Killed

[InfoSec812]

I have a project using Postgres/Mailpit/Keycloak DevServices containers (via TestContainers and Podman). On my MacBook, everything works fine. On my Linux machine (14core/20thread 64GB RAM) the Keycloak container is "killed" every time with the following log output:

❯ podman logs -f practical_wiles
Changes detected in configuration. Updating the server image.
Updating the configuration and installing your custom providers, if any. Please wait.
/opt/keycloak/bin/kc.sh: line 169:    82 Killed                  'java' -Dkc.config.build-and-exit=true -Djava.util.concurrent.ForkJoinPool.common.threadFactory=io.quarkus.bootstrap.forkjoin.QuarkusForkJoinWorkerThreadFactory '-XX:MetaspaceSize=96M' '-XX:MaxMetaspaceSize=256m' '-Dfile.encoding=UTF-8' '-Dsun.stdout.encoding=UTF-8' '-Dsun.err.encoding=UTF-8' '-Dstdout.encoding=UTF-8' '-Dstderr.encoding=UTF-8' '-XX:+ExitOnOutOfMemoryError' '-Djava.security.egd=file:/dev/urandom' '-XX:+UseG1GC' '-XX:FlightRecorderOptions=stackdepth=512' '-XX:MaxRAMPercentage=70' '-XX:MinRAMPercentage=70' '-XX:InitialRAMPercentage=50' '--add-opens=java.base/java.util=ALL-UNNAMED' '--add-opens=java.base/java.util.concurrent=ALL-UNNAMED' '--add-opens=java.base/java.security=ALL-UNNAMED' '-Duser.language=en' '-Duser.country=US' -Dkc.home.dir='/opt/keycloak/bin/..' -Djboss.server.config.dir='/opt/keycloak/bin/../conf' -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dpicocli.disable.closures=true -Dquarkus-log-max-startup-records=10000 -cp '/opt/keycloak/bin/../lib/quarkus-run.jar' io.quarkus.bootstrap.runner.QuarkusEntryPoint 'start' '--http-enabled=true' '--hostname-strict=false' '--spi-user-profile-declarative-user-profile-config-file=/opt/keycloak/upconfig.json'

I have tried all sorts of things trying to determine why it's happening:

• Enable/Disable RYUK
• Change the DOCKER_HOST env variable
• Change the ~/.testcontainers.properties in various ways
• Disable my imported realm.json file

I even updated to the latest Quarkus 3.18.4 (from 3.18.1) with no improvement. Does anyone have any ideas?

[quarkus-bot[bot]]

/cc @geoand (devservices), @pedroigor (keycloak), @sberyozkin (keycloak)

[sberyozkin]

@InfoSec812 It is only a guess but it might be caused by OOM due to the Keycloak container requiring more memory than is allowed by the containerMemoryLimit.

Setting it to a larger value might help

[InfoSec812]

I tried setting it to 2G and I am still getting the same result.

[InfoSec812]

NVM, I spoke too soon. I had set quarkus.keycloak.devservices.containerMemoryLimit and the actual key should be container-memory-limit. It's working now! Thanks @sberyozkin