Loading SNOMED CT FULL in a Docker installation

[eirikconteir]

Hi,

I try, without success, to load SNOMED CT with full history into a couple of Snowstorms installed using docker-compose.

I've tried to "load a SNOMED CT release directly into the running docker container using the loading SNOMED instructions." But the next step fails:

java -Xms2g -Xmx4g -jar target/snowstorm*.jar --delete-indices --import-full=<Absolute-path-of-SNOMED-CT-RF2-zip>

... because the .jar file can't be found.

Loading SNAPSHOTs into Snowstorm MAIN using the API works beautifully, but I'm denied to load a full version of MAIN using the API because the branch contains content (even thought it's a clean installation).

Could you please tell me if I do anything wrong, or update the documentation?

Best from Oslo,

Eirik

[kaicode]

Hi @eirikconteir,

We recently updated the way we package Snowstorm for Docker. The instructions are still accurate for a plain Java installation. To start Snowstorm within Docker with the delete-indicies and import-full flags it would look something like this:

java -Xms2g -Xmx4g --add-opens java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED -cp @/app/jib-classpath-file org.snomed.snowstorm.SnowstormApplication --elasticsearch.urls=http://es:9200 --delete-indices --import-full=<Absolute-path-of-SNOMED-CT-RF2-zip>

Please note that the FULL import only supports Edition type packages being imported onto the MAIN branch. Examples of Edition packages are the International Edition and the US Edition. Importing the history of extension packages is not yet supported.

[eirikconteir]

Thank you, @kaicode . I still have issues.

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2023-11-13 11:07:27.691 ERROR 86 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter   : 

***************************
APPLICATION FAILED TO START
***************************

Description:

Web server failed to start. Port 8080 was already in use.

Action:

Identify and stop the process that's listening on port 8080 or configure this application to listen on another port.

2023-11-13 11:07:27.723  INFO 86 --- [-status-polling] o.s.s.c.d.s.c.ClassificationService      : Classification status polling thread stopped.

I have tried to resolve the possible port conflict

95a05cb13242 snomedinternational/snowstorm:latest "java -Xms2g -Xmx4g …" 3 minutes ago Up 3 minutes 0.0.0.0:8081->8080/tcp, :::8081->8080/tcp snowstorm

... but with no success

[kaicode]

Restarting the container should ensure that the other Snowstorm process is stopped.