singularity icon indicating copy to clipboard operation
singularity copied to clipboard

Supporting both CMD and ENTRYPOINT for converted Docker images

Open jakirkham opened this issue 7 years ago • 3 comments

Would be nice if Singularity supported both CMD and ENTRYPOINT of converted Docker images. This can be useful if there are some steps that always should be run at container startup (e.g. in the ENTRYPOINT) and default steps than can be optionally replaced (e.g. CMD).

As an example from personal experience, it can be quite handy to run all activation scripts in ENTRYPOINT and then drop users into a shell set by CMD. Though users may want to do different things, than just get a shell (e.g. start a web server). It's handy to ensure the activation scripts still get run so that things behave how the user expects. Otherwise users are stuck hunting through Dockerfiles looking for what the ENTRYPOINT did (assuming they are able to do even that).

jakirkham avatar Sep 06 '18 18:09 jakirkham

Hello,

This is a templated response that is being sent out to all open issues. We are working hard on 'rebuilding' the Singularity community, and a major task on the agenda is finding out what issues are still outstanding.

Please consider the following:

  1. Is this issue a duplicate, or has it been fixed/implemented since being added?
  2. Is the issue still relevant to the current state of Singularity's functionality?
  3. Would you like to continue discussing this issue or feature request?

Thanks, Carter

carterpeel avatar May 15 '21 16:05 carterpeel

This issue has been automatically marked as stale because it has not had activity in over 60 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jul 14 '21 17:07 stale[bot]

@jakirkham Still getting this problem ? Have this been solved already ? If yes, what work around have you followed and applied ?

We're looking into the issue carefully, soon will bring to community and discuss ways to better solve as well address this. Thankyou for keeping the interest in the subject.

pedroalvesbatista avatar Jul 15 '21 01:07 pedroalvesbatista

Old Singularity repo issues are now closed. If this is still critical please open a new issue in Apptainer repo.

kmuriki avatar Aug 16 '22 01:08 kmuriki

Do you have a blogpost entry (link) about this change?

jakirkham avatar Aug 16 '22 04:08 jakirkham

Do you have a blogpost entry (link) about this change?

No, it has not been changed. If you still think it's important, please create an issue in the current repo referring back to this one.

DrDaveD avatar Aug 17 '22 16:08 DrDaveD

Sorry maybe that was too vague. My question was about this larger overhaul. Think the blogpost (below) may answer that, but it is possible that I'm still missing things (please feel free to guide me to better resources if so :)

https://apptainer.org/news/community-announcement-20211130/

jakirkham avatar Aug 17 '22 16:08 jakirkham

Oh, right. Yes that's the best explanation of the switch from Singularity to Apptainer.

DrDaveD avatar Aug 17 '22 21:08 DrDaveD

There's also this documentation in the admin guide that explains the migrating from Singularity to Apptainer and that links to the user guide discussion on compatibility between the two.

DrDaveD avatar Aug 17 '22 21:08 DrDaveD

Thanks that's very helpful 🙏

Maybe those links are worth including in that blogpost?

jakirkham avatar Aug 17 '22 22:08 jakirkham

I don't think we should revise that historical announcement because those guides weren't there at the time, but there should be a news announcement about the 1.0.0 release and the links included there.

DrDaveD avatar Aug 18 '22 15:08 DrDaveD