8000 Replace CMD with ENTRYPOINT · Issue #37 · TheJacksonLaboratory/SVE · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Replace CMD with ENTRYPOINT #37

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.

Sign up for GitHub

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

Jump to bottom
Open
mcuma opened this issue Mar 10, 2020 · 1 comment
Open

Replace CMD with ENTRYPOINT #37

mcuma opened this issue Mar 10, 2020 · 1 comment

Comments

@mcuma
Copy link
mcuma commented Mar 10, 2020

No description provided.

@mcuma
Copy link
Author
mcuma commented Mar 10, 2020

Hello,

please modify your Dockerfile and the Dockerhub container to replace
CMD ["/tools/SVE/bin/sve"]
with
ENTRYPOINT["/tools/SVE/bin/sve"]

ENTRYPOINT is the correct way to specify what the container needs to run when it's "executed", as described in https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact. CMD specifies the arguments to the ENTRYPOINT command.

The current setup causes problems when we pull the Docker container using Singularity and run it as a Singularity container, e.g.
$ singularity build sve docker://wanpinglee/sve
$ singularity run sve call
/.singularity.d/runscript: 39: exec: call: not found

i.e., Singularity (correctly) replaces the CMD in the container with the "call" argument and runs just that on an empty entrypoint, which results in the error above.

Thanks,
MC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mcuma
0