Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ePadjs deployed by docker does not work #1

Closed
minhhungvu17 opened this issue Dec 19, 2019 · 2 comments
Closed

ePadjs deployed by docker does not work #1

minhhungvu17 opened this issue Dec 19, 2019 · 2 comments

Comments

@minhhungvu17
Copy link

minhhungvu17 commented Dec 19, 2019

Hi Rubin Lab, I'm trying to deploy ePad for medical image annotation. However, there is a small problem

Problem

ePadjs does not work after installation via dockers.

Steps to reproduce

  1. Open the ports:
  • 3000
  • 8080
  • 8090
  • 8899
  1. Install docker
  2. Replace http://epad-build.stanford.edu with localhost ip in the files mentioned in the installation guide
  3. Run docker-compose up --build -d

Expected Behavior

ePadjs web runs and goes to login page

Actual behavior

ePadjs does not direct to login page to access private modules

ePadjs running on Chrome
Capture d’écran 2019-12-19 à 4 12 15 PM
Docker checking
Capture d’écran 2019-12-19 à 4 11 47 PM

Thank you for your help!

@emelalkim
Copy link
Contributor

emelalkim commented Dec 19, 2019

Hi,
I think this issue is actually related to the epadlite beta distribution files in ftp not this project. This project is focused on automating the edits on the configuration files.
I suggest you use this project to generate the configuration files for your system as your issue is most probably caused by problems in your configuration files. If you use the sample yml file in this project and edit the host and required credentials, you can get the daily build.
If you want to use the beta images instead, you can check the readme and modify mode and image attributes for each module (Let us know if you need help with that) Actually, these files (docker-compose) won't work with beta images since we changed the code directory structure in the images to run with non root user. We'll have the docker images of the first release soon.
Nonetheless, your issue is most probably caused by the wrong value in production_keycloak.json file. In chrome you can right click, open Inspect and check console and network to see what is the issue.

@minhhungvu17
Copy link
Author

@emelalkim thank you so much for your suggestion. The issue was solved so I will close this ticket. Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants