RubinLab / epad-dist

5 stars 5 forks source link

Starting docker-compose failed #25

Closed dsernahiguita closed 3 years ago

dsernahiguita commented 3 years ago

I am trying to install epad_lite in my mac: macOS Catalina version 10.15.7 Docker desktop: version 2.1.0.1

but I got the following error:

_Creating an optimized production build... _The build failed because the process exited too early. This probably means the system ran out of memory or someone called kill -9 on the process. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! ejs@0.1.0 build: react-scripts --max_old_space_size=4096 build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the ejs@0.1.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/node/.npm/_logs/2020-10-29T19_39_35_676Z-debug.log ERROR: Service 'myepadjs' failed to build: The command '/bin/sh -c npm run build' returned a non-zero code: 1__

The setup of my epad.yml is: _host: localhost mode: lite config: environment cache: size: "10g" inactivetime: "60m" compression: minsize: "20" keycloak: mode: build dockerfiledir: ".\/keycloak" user: admin password: vivamed123 email: vivamed@eafit.edu.co port: 8899 loc: "keycloak" couchdb: mode: image image: "2.3.1" user: admin password: admin port: 8888 dblocation: "..\/couchdbloc" dicomweb: mode: build dockerfiledir: ".\/dicomweb-server" port: 8090 dbname: chronicle log: true auth: none loc: "pacs" epadlite: mode: build dockerfiledir: ".\/epadlite" port: 8080 dbname: epadlite log: true https: false auth: auth loc: "api" epadjs: mode: build dockerfiledir: ".\/epadjs" port: 80 mariadb: mode: image image: latest dbname: epaddb user: admin password: admin rootpassword: admin port: 3306 log: false backuploc: ".\/epaddbnodata.sql" dblocation: "..\/mariadbloc"

The setup of the docker-compose is:version: "3" services: myepadjs: build: ./epadjs container_name: epad_js expose:

Thanks in advance Diana Lucia Serna Higuita

emelalkim commented 3 years ago

hi, I suspect the reason build fails is the amount of ram available to the container. epadjs needs 4gb ram to be able to build. another issue i see with your configuration is you are using localhost as your hostname. unfortunately, you cannot use that as inside the containers localhost resolves to the container itself. you need to use the ip or the shared hostname of the machine. you can enable sharing and use the .local hostname that you see in sharing settings. you can also use the installation script to get/fix ip. @acavit can give more information about that

dsernahiguita commented 3 years ago

Hi, really thank you very much for your prompt response. I was checking the free ram and I have approximately 4.75G free:

Bildschirmfoto 2020-10-29 um 22 01 23

so I guess the problem could be the localhost, I had changed the epad.yml to use 127.0.0.1 (instead localhost), but still when I try to run the docker compose I got the same issue

  1. Could you please let me know where I can find the installation script to get/fix ip and how can I use it?

epad.yml: host: 127.0.0.1 mode: lite config: environment cache: size: "10g" inactivetime: "60m" compression: minsize: "20" keycloak: mode: build dockerfiledir: ".\/keycloak" user: admin password: vivamed123 email: vivamed@eafit.edu.co port: 8899 loc: "keycloak" couchdb: mode: image image: "2.3.1" user: admin password: admin port: 8888 dblocation: "..\/couchdbloc" dicomweb: mode: build dockerfiledir: ".\/dicomweb-server" port: 8090 dbname: chronicle log: true auth: none loc: "pacs" epadlite: mode: build dockerfiledir: ".\/epadlite" port: 8080 dbname: epadlite log: true https: false auth: auth loc: "api" epadjs: mode: build dockerfiledir: ".\/epadjs" port: 80 mariadb: mode: image image: latest dbname: epaddb user: admin password: admin rootpassword: admin port: 3306 log: false backuploc: ".\/epaddb_nodata.sql" dblocation: "..\/mariadbloc"

dsernahiguita commented 3 years ago

Hi :) I found the issue, I had extended the ram to 4G in docker settings and now the instalation is successfully... maybe you can add this information to the Readme

thanks a lot for your help

Diana