You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This version is extremely outdated and uses and old docker image format and manifest specification. This can be shown by pulling the container using docker:
docker pull quay.io/biocontainers/fastqc:0.11.9--0
[DEPRECATION NOTICE] Docker Image Format v1, and Docker Image manifest version 2, schema 1 support will be removed in an upcoming release. Suggest the author of wave.seqera.io/wt/870285518668/biocontainers/fastqc:0.11.9--0 to upgrade the image to the OCI Format, or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs
Amazon AWS batch seems to have removed support for these old specification as this started breaking between May 31st 2024 and June 10th 2024. Updating the fastqc container version fixes this issue. An updated nf-core module version for fastqc is already included in the dev branch, so nothing needs to be done beside a new release soon!
A current fix for anybody running into this with version 2.6.0 is to add the following to your nextflow.config:
Description of the bug
The current container version used by viralrecon release 2.6.0 for FASTQC modules is 0.11.9.
This version is extremely outdated and uses and old docker image format and manifest specification. This can be shown by pulling the container using docker:
Amazon AWS batch seems to have removed support for these old specification as this started breaking between May 31st 2024 and June 10th 2024. Updating the fastqc container version fixes this issue. An updated nf-core module version for fastqc is already included in the dev branch, so nothing needs to be done beside a new release soon!
A current fix for anybody running into this with version 2.6.0 is to add the following to your nextflow.config:
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: