Wave error when using SHA256 as tag does not support the containerConfig

[evanfloden]

Running a Nextflow pipeline where one of the processes is defined using a SHA256 container.

Error message:

Wave invalid response: [400] {"message":"Container requests made using a SHA256 as tag does not support the 'containerConfig' attribute"

Container is defined in the process:

container python@sha256:a2d01031695ff170831430810ee30dd06d8413b08f72ad978b43fd10daa6b86e

Running on Seqera with AWS Batch using Forge + Wave.

[ewels (Phil Ewels)]

This is expected - we’re halfway through adding docs describing this here:

Describe use of sha256 hash with Wave

Copied below for convenience:

---

Reproducible builds with SHA256 container image references

Referring to the SHA256 hash of a container imagine is a common best practice in pipeline development. For example, the SHA256 hash for a container might be similar to sha256:3235...ce8f. If you use the Wave service to augment your containers, such as to add Fusion to a container, the original SHA256 hash of the image is no longer correct.

To accommodate the new layers added to a container image augmented with Wave, you can use the freeze feature of Wave. In your pipeline configuration, ensure that you specify the following settings:

wave.enabled = true
wave.freeze = true
wave.strategy = ['dockerfile']
wave.build.repository = 'docker.io/<user>/<repository>'

You can run nextflow inspect to find the SHA256 hash of the Wave augmented container.

In your pipeline, you can use the SHA256 of the Wave augmented container, available in the target repository that you specify with the wave.build.repository parameter. For example:

docker.enabled = true
process.container = 'docker.io/<user>/my-bio-container@sha256:3235....ce8f'

[ewels (Phil Ewels)]

I created an issue specifically about improving the error message that’s returned:

Improve error message when augmenting with a sha256 tag