-
Notifications
You must be signed in to change notification settings - Fork 3
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 run command returning "is not a file" error on omex path #60
Comments
After doing some deep diving, I have mapped out the general schema for the container which is created by the Dockerfile within this repo using a JSON-like object. The schema is: { May this serve as a mapping for Dockerfile traversal. |
Without error, I am able to call:
docker pull {copasi image str}
However, when calling:
docker run {copasi image str} -i {path to omex} -o {path to output}
I am greeted with the following error:
{path to omex} is not a file
I have taken care to point to a .omex file and NOT the directory of omex contents.
PROPOSAL:
Refactoring docker abilities to recursively index a desired omex path. PR to come.
The text was updated successfully, but these errors were encountered: