Closed nr23730 closed 3 months ago
@nr23730 I can replicate with the latest release.
docker pull hapiproject/hapi:latest-tomcat
docker run -p 8080:8080 <generated-image-id>
I was looking into a different issue regarding Tomcat (build related), and recently tested against that build:
https://github.com/hapifhir/hapi-fhir-jpaserver-starter/pull/720
When running off that image, I DO get a working HAPI (I can run all the smoketest files without error).
I built and tested as follows:
Built with `docker build --target tomcat . `
Started the new image in a container with `docker run -p 8080:8080 <generated-image-id>`
Ran the smoke tests against container (https://github.com/hapifhir/hapi-fhir-jpaserver-starter/blob/master/src/test/smoketest/plain_server.http)
If that PR is approved, it will be used in the next release. Comments in the PR would be appreciated.
Out of curiosity @nr23730 - how come you use the tomcat variant and not the distroless?
It's way more responsive when you just use it every now and then.
@nr23730 could you try building the tomcat image using this branch: rel_7_3_tracking?
Works as expected. Thank you very much!
Starting with 7.0.0 all docker images (docker.io/hapiproject/hapi) with the
-tomcat
suffix won't start HAPI-FHIR. This is even though tomcat claims that the app will be deployed (see logs below) Version 6.10.1 works correctly.