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

MD Express: Issues with .env and docker-compose file #141

Open
chezhia opened this issue Sep 29, 2023 · 0 comments
Open

MD Express: Issues with .env and docker-compose file #141

chezhia opened this issue Sep 29, 2023 · 0 comments
Assignees

Comments

@chezhia
Copy link

chezhia commented Sep 29, 2023

There are 2 minor issues with the MD Express docker-compose.yml and .env file that prevents launching the services without modifications:

  1. In the .env file, the TASK_MANAGER_DATA has an additional $PWD that is not present in other DATA variables and throws an error when launched. The error arises due to docker-compose assuming $PWD as a named volume.

Named volume "$PWD/.md/mdtm:/var/lib/monai:rw" is used in service "task-manager" but no declaration was found in the volumes section.

Edit - Saw this issue in the FAQ section, Why does only the TASK_MANAGER_DATA need $PWD though? isn't .md/ already assuming the docker-compose up is run from the MDE working directory?

  1. If the idea is to use the .env file to set the desired data directories, the data volume for elasticsearch service should also be defined there, instead of directly assigning it to .md/esdata in the docker-compose.yml file.
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