Munish Chouhan

@mribeirodantas What is the goal here? should we just. add a log entry stating user is using defaults channel?

@itrujnara thanks for reporting the issue --freeze works without --build-repository only for conda packages and not for custom Dockerfile That is a special case, where we use community.seqera.io as --build-repository...

> What is this solving? This was created to assist with the changes in UI to replace the current refresh mechanism @joaquimgamero was working on it. Can you please point...

It works in case of freeze because Wave adds config in the containerfile before generating the container ID https://github.com/seqeralabs/wave/blob/647edc52861d86eb0d64ff640e12846b7b9e2dbf/src/main/groovy/io/seqera/wave/service/builder/FreezeServiceImpl.groovy#L155

tested for build: ``` % wave --conda-package bwa --wave-endpoint http://localhost:9090 Wave invalid response: [501] {"message":"Build service is not enabled - Check Wave configuration setting 'wave.build.enabled' - HTTP status=501 - response=-"}...

tested as proxy: ``` % wave -i ubuntu --wave-endpoint http://localhost:9090 wave.eu.ngrok.io/wt/c21012677872/library/ubuntu:latest ```

tested mirroring: ``` % wave -i quay.io/biocontainers/bwa:0.7.15--0 --mirror --build-repository docker.io/hrma017 --tower-token --wave-endpoint http://localhost:9090 --tower-endpoint http://localhost:8000/api Wave invalid response: [501] {"message":"Mirror service is not enabled - Check Wave configuration setting 'wave.mirror.enabled'...

Tested augmentation: ``` % wave -i ubuntu --config-file https://fusionfs.seqera.io/releases/v2.5-amd64.json --wave-endpoint http://localhost:9090 wave.eu.ngrok.io/wt/504999fe3eb4/library/ubuntu:latest ```

@pditommaso, should we add a message for scan mode too? ``` % wave -i ubuntu --scan-mode required --await --wave-endpoint http://localhost:9090 wave.eu.ngrok.io/wt/0d4b4710ca43/library/ubuntu:latest ```

> Currently what error is returning? Currently no error, it return the image URL and scan does not get triggered