In our pipeline nf-core/molkart, we need to overwrite the entrypoint setting for docker because some of the containers for processes not maintained by us define Entrypoints ( molkart/nextflow.config at 7605a53092930a0b65509c64f79834a6c8449e9b · nf-core/molkart · GitHub ). The current AWS Megatests fo…

Interesting problem! :smile: What is happening is these: Fusion needs to be the entrypoint of the container to be sure that it’s the init process and all the subprocesses will be able to access Fusion filesystem. To achieve this, Wave is changing the entrypoint of the image to /usr/bin/fusion but…

AWS Megatests failing due to entrypoint overwrite not being applied to wave

Ask for help

ewels (Phil Ewels) February 14, 2024, 3:36pm 4

@FloWuenne - given that this process only supports the Docker container and not Conda / anything else. Is there any reason not to just truncate the process script to this?

mesmer ...

Topic		Replies	Views
Passing Docker runOptions over to Wave Ask for help	4	237	February 22, 2024
Nf-core/pangenome aws-megatests fail - maybe because of fusion or wave? Ask for help fusion , aws , nf-core	4	168	March 1, 2024
Dealing with executable docker image Ask for help nextflow , nf-core	4	168	May 29, 2024
Wave error when using SHA256 as tag does not support the containerConfig Ask for help	2	124	April 29, 2024
Wave invalid response: [400] {"Container image does not exist or access is not authorized"} Ask for help nextflow , nf-core	7	35	November 1, 2024

AWS Megatests failing due to entrypoint overwrite not being applied to wave

Related topics