Seqera Platform should ignore hard-coded ENTRYPOINTs
acknowledged
Y
Yarrow Bison
Seqera Platform won't accept Docker images that have an
ENTRYPOINT
. Nextflow itself (on my laptop) successfully ignores a hardcoded ENTRYPOINT
and runs the Nextflow task bash script. Our devs stumble over this from time to time and can't debug the issue without help from one of our NF experts. Additionally, this slows down our transition from other workflow runners that require an ENTRYPOINT
. Would it be possible to have Seqera Platform also ignore hard-coded ENTRYPOINTs?Currently we make an extra Dockerfile and image like this:
FROM <other image>
ENTRYPOINT []
This leads to confusing clutter in our repos and artifact store. I hear that one cannot use the workaround of setting a container option with an empty entrypoint because of an incompatibility with Fusion
F
Fellow Bee
Hi, what do you mean "Seqera Platform won't accept Docker images that have an
ENTRYPOINT
"? Platform just uses Nextflow for running a workflow execution, as such does not alter or expect any specific entrypoint setting. Conversely, not sure it's correct to say Nextflow ignores the entrypoint. Nextflow runs the task passing the script to be executed as a container command (
CMD
), as such it expected to entrypoint to be the linux shell (sh
or bash
). If the container entrypoint is defined a as a non-shell command your task execution will fail.
Rob Newman
acknowledged