Docker image - server fails to initialise correctly

The Docker image pulled from ibmcom/ibm-fhir-server fails to start correctly.

To Reproduce Steps to reproduce the behavior:

1. Pull the Docker image from https://hub.docker.com/r/ibmcom/ibm-fhir-server
2. Ensure Docker Desktop is running (I am using Windows 10)
3. In a bash shell in WSL2, start an instance of the image using docker run -p9443:9443 ibmcom/ibm-fhir-server
4. Once the server appears to have started, use the recommended health-check: curl -k -i -u 'fhiruser:change-password' 'https://localhost:9443/fhir-server/api/v4/$healthcheck'
5. Observe the console output.

Expected behavior FHIR server startup, followed by a successful health check.

Observations The console output suggests an issue with the embedded Derby database:

[ERROR   ] Encountered an exception while bootstrapping the FHIR database
java.sql.SQLNonTransientConnectionException: No current connection.

And the servlet context fails to initialise:

[ERROR   ] SRVE0283E: Exception caught while initializing context: java.lang.RuntimeException: Encountered an exception while initializing the servlet context.
        at com.ibm.fhir.server.listener.FHIRServletContextListener.contextInitialized(FHIRServletContextListener.java:208)
        at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:2433)

Additional context My environment: Windows 10 Professional Edition Version 10.0.18363 Build 18363 Docker Desktop: v3.1.0 Docker Engine: v20.10.2 Using the WSL2 integration.

I have saved a complete copy of the console output in a public gist: https://gist.github.com/searjeant/1ba53621abe92cc783eec0a9a3969574

I did read (and re-read) the configuration documentation on the Docker Hub page, but I wanted to ensure I could start the default container first, before making any of the changes described on that page.

Apologies if I have missed something obvious - I’d appreciate a hint.

[prb112]

@danarteaga @searjeant I hope all is well. If there is any followup, we’re happy to re-open.

Keep asking questions/opening bugs, we’ll work on it.

[prb112]

Right, it’s the allocated resources in your Docker setup. You can cap the total cores and available memory.