Tower monitoring failing with a Wave Conda container

[marcodelapierre]

$ nextflow info
  Version: 22.12.0-edge build 5830
  Created: 13-12-2022 21:22 UTC 
  System: Linux 5.15.0-58-generic
  Runtime: Groovy 3.0.13 on Java HotSpot(TM) 64-Bit Server VM 19.0.2+7-44
  Encoding: UTF-8 (UTF-8)

$ nextflow run marcodelapierre/toy-cowsay-nf -profile condawave -r main -with-tower
[..]
Command error:
  Unable to find image 'wave.seqera.io/wt/2a2b94a788ad/wave/build:fd8de55a0b747597234e1c02d7cf5c40' locally
  fd8de55a0b747597234e1c02d7cf5c40: Pulling from wt/2a2b94a788ad/wave/build
  Digest: sha256:6a69a0c644bb02bbd8f24e00a1117af20dc08709db06a062a011b044d7613551
  Status: Image is up to date for wave.seqera.io/wt/2a2b94a788ad/wave/build:fd8de55a0b747597234e1c02d7cf5c40
  Command 'ps' required by nextflow to collect task metrics cannot be found
[..]

The image is downloaded at last, so the issue is Command 'ps' required by nextflow to collect task metrics cannot be found.
Should this be automatically added to every Wave container?

[marcodelapierre]

@pditommaso thoughts?

[pditommaso]

Welcome to the hell :D. I think it should not, Wave should not alter the user container if not explicitly required.

Currently workaround is to install in with this trick, but I agree something better it would be nice

[marcodelapierre]

We could analyse which files in the repo get added/edited with that installation.
Once reviewed that, I would add that line to the Dockerfile template. If it is required to run with Wave/Tower effectively, I would say it should be in the default dockerfile, same as a compiler, or runtime library, would be. We can declare it in the Wave docs for transparency.

[marcodelapierre]

Would be closed by nextflow-io/nextflow#3615