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

There is NO need to add run_dbcan in docker run command #114

Open
bladrome opened this issue Mar 24, 2023 · 2 comments
Open

There is NO need to add run_dbcan in docker run command #114

bladrome opened this issue Mar 24, 2023 · 2 comments

Comments

@bladrome
Copy link

docker run --name <preferred_name> \
-v <host-path>:<container-path> \
-it haidyi/run_dbcan:latest \
run_dbcan <input_file> [params] \
--out_dir <output_dir>
@apduncan
Copy link

apduncan commented Dec 1, 2023

I encountered the same with the latest Docker image. Including run_dbcan as suggested in the Readme, it was getting consumed as the first argument. Given run_dbcan is the entrypoint in the Dockerfile, could the documentation be updated to give the docker command as

docker run --name <preferred_name> -v <host-path>:<container-path> -it haidyi/run_dbcan:latest <input_file> {protein,meta,prok} [params] --out_dir <output_dir>

@linnabrown
Copy link
Owner

Thank you so much @apduncan , we currently updating a new version for a more comprehensive pipeline and will integrate this new command.

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

3 participants