member badge
Ken Brewer
Seqera Platform currently allows users to configure the
launchContainer
that runs the Nextflow head job in a limited number of ways:
  1. Enterprise Deployment Configuration (Seqera Platform Enterprise only)
  • Custom Nextflow Launcher images can be specified in the deployment configuration (docs)
Note:
Modifying this image requires Platform node restarts
  1. API-Level Launch Container Specification (Enterprise & Cloud)
  • The
    launchContainer
    parameter in the
    Create Action
    API endpoint allows you to set the orchestrator image for pipelines triggered via Seqera Actions.
  • The
    launchContainer
    parameter in the
    Create Pipeline
    API endpoint allows you to set the orchestrator image for pipelines triggered via UI launchpad entries.
  • The
    launchContainer
    parameter in the
    Launch Workflow
    API endpoint allows per-workflow orchestrator image specification.
These parameters are currently accessible only via the API and our Terraform provider. There is no corresponding UI option, which forces users to rely on the API for a core part of pipeline, action, and launch configuration.
Proposed Solution 1
  • Add a
    launchContainer
    option to the Create Pipeline page
  • Add a
    launchContainer
    option to the edit pipeline page
  • Add a
    launchContainer
    option to the Create Action page
Proposed Solution 2
In terms of platform usage, it probably makes more sense to set the
launchContainer
at the compute environment level. This matches the needs of large pharma customers that need to customize proxies and networking certificates used in these
launchContainers
.