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

Docker mmpdb.py error #1

Closed
MKCarter opened this issue Jan 2, 2023 · 1 comment
Closed

Docker mmpdb.py error #1

MKCarter opened this issue Jan 2, 2023 · 1 comment
Assignees

Comments

@MKCarter
Copy link

MKCarter commented Jan 2, 2023

Hey,

Trying to run this, but I seem to be unable to run the mmpdb.py when running the docker compose up command. This is the error I am obtaining:

matcher-backend-1   | python: can't open file '/opt/./mmpdb/mmpdb.py': [Errno 2] No such file or directory
matcher-backend-1   | ERROR conda.cli.main_run:execute(49): `conda run python ./mmpdb/mmpdb.py fragment ./initialize_db/quick_structures.smi -o ./initialize_db/quick_structures.fragments --cut-smarts matcher_alpha` failed. (See above for error)
matcher-backend-1 exited with code 1

Do you have any thoughts on how to fix this?

@hooveran
Copy link
Collaborator

hooveran commented Jan 11, 2023

Hey @MKCarter,

It seems like you may not have downloaded the required mmpdb submodule. You can check whether this is the case by looking in the matcher/backend/mmpdb directory, in your local matcher repository.

The contents of this mmpdb directory (submodule) are not automatically downloaded when cloning the matcher repository; these additional steps are necessary:

  1. Navigate to your local matcher repository (the parent matcher folder)
  2. Execute git submodule init, and then git submodule update. This should download all the mmpdb code into the location matcher/backend/mmpdb

The below commands are only necessary if you've already run docker-compose, and you want to update your docker setup with the new code. If you hadn't previously run docker-compose, the below steps wouldn't be necessary.

  1. Rebuild your local docker images to incorporate this newly downloaded code: docker-compose build (this command comprehensively rebuilds all images from source, although it is likely that only the backend container needs to be rebuilt)
  2. Launch a fresh set of containers from the updated images: docker-compose up --force-recreate

Please let us know if there are further issues. Thanks!

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