Running KeyCloak in Azure Container App

Hi,

I am trying to configure KeyCloak to run inside an Azure Container App. I have followed the instructions for creating a Dockerfile. When I start the container I get the following log:

2024-07-04T13:41:53.14723 Connecting to the container ‘fusionauth’…

2024-07-04T13:41:53.16793 Successfully Connected to container: ‘fusionauth’ [Revision: ‘fusionauth-test–btdsast-6858498bb8-jv64w’, Replica: ‘fusionauth-test–btdsast’]

2024-07-04T13:41:57.845645845Z Updating the configuration and installing your custom providers, if any. Please wait.

2024-07-04T13:42:31.945515692Z 2024-07-04 13:42:22,146 WARN [org.key.services] (build-19) KC-SERVICES0047: magic-link (io.phasetwo.keycloak.magic.resources.MagicLinkResourceProviderFactory) is implementing the internal SPI realm-restapi-extension. This SPI is internal and may change without notice
2024-07-04T13:42:31.946359143Z 2024-07-04 13:42:24,246 WARN [org.key.services] (build-19) KC-SERVICES0047: ext-magic-form (io.phasetwo.keycloak.magic.auth.MagicLinkAuthenticatorFactory) is implementing the internal SPI authenticator. This SPI is internal and may change without notice
2024-07-04T13:42:31.946967126Z 2024-07-04 13:42:26,648 WARN [org.key.services] (build-19) KC-SERVICES0047: ext-magic-link (io.phasetwo.keycloak.magic.auth.token.MagicLinkActionTokenHandlerFactory) is implementing the internal SPI actionTokenHandler. This SPI is internal and may change without notice

2024-07-04T13:43:06.665087077Z /opt/keycloak/bin/kc.sh: line 169: 78 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 --profile=dev start-dev

I am assuming the kc.sh line 169 78 Killed means something, nut I have no idea what. Can anyone help - I am just starting with keyCloak.

Thanks
Alan