B
Brass Wildcat
Wave is used for container authentication or to enable running Fusion in pipelines. However, when Wave is enabled, the container's name reported in the task table is modified to include the hostname of the Wave service and a unique temporary token. This results in container names like "wave.seqera.io/wt/1234567890/nextflow/bash:latest" instead of the expected "nextflow/bash:latest." This may be perceived as an undesired side effect or even an error in the system.
Our goal is to improve the transparency of Wave containerization. In the task table, we aim to display the expected container name for each task and provide users with the ability to inspect the associated Wave container metadata.
Proposed Solution
When rendering the tasks table, the system should identify the use of a Wave container and take the following actions:
  1. Remove the Wave-specific prefix and display the original container name, e.g., "nextflow/bash:latest."
  2. Introduce a visual identifier (e.g., an icon or badge) to mark the container as a "Wave" container.
  3. Make the container name a link, allowing users to access the corresponding container metadata information page.
  4. On the container metadata page, report the information presented at this reference link.