# Wave invalid response: POST https://wave.seqera.io/v1alpha2/container \[400\] {"message":"Container image 'biocontainers/stringtie:2.2.3--h43eeafb\_0' does not exist or access is not authorized"}

**URL:** <https://community.seqera.io/t/wave-invalid-response-post-https-wave-seqera-io-v1alpha2-container-400-message-container-image-biocontainers-stringtie-2-2-3-h43eeafb-0-does-not-exist-or-access-is-not-authorized/2376>\
**Category:** Ask for help\
**Tags:** nextflow, platform\
**Created:** [September 23, 2025, 4:09pm UTC](https://community.seqera.io/t/wave-invalid-response-post-https-wave-seqera-io-v1alpha2-container-400-message-container-image-biocontainers-stringtie-2-2-3-h43eeafb-0-does-not-exist-or-access-is-not-authorized/2376 "2025-09-23T16:09:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kokul-atx](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/kokul-atx/32/2063_2.png) [@kokul-atx](https://community.seqera.io/u/kokul-atx)\
**Post date:** [September 23, 2025, 4:09pm UTC](https://community.seqera.io/t/wave-invalid-response-post-https-wave-seqera-io-v1alpha2-container-400-message-container-image-biocontainers-stringtie-2-2-3-h43eeafb-0-does-not-exist-or-access-is-not-authorized/2376/1 "2025-09-23T16:09:48Z")

</div>

Hi all,  
I am trying to run a custom pipeline on seqera cloud platform that were developed based-on nf-core modules. I run into issues with the latest nf-core/modules for rseqc and stringtie for which wave containers cannot be found.

```auto
Wave invalid response: POST https://wave.seqera.io/v1alpha2/container [400] {"message":"Container image 'biocontainers/stringtie:2.2.3--h43eeafb_0' does not exist or access is not authorized"}

 Wave invalid response: POST https://wave.seqera.io/v1alpha2/container [400] {"message":"Container image 'biocontainers/rseqc:5.0.3--py39hf95cd2a_0' does not exist or access is not authorized"}

```

What is the best way to resolve this issue?

Thanks

Best,  
Kokul

---

<div class="post-metadata">

**Author:** ![FlorianWuennemann](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/florianwuennemann/32/638_2.png) [@FlorianWuennemann](https://community.seqera.io/u/FlorianWuennemann)\
**Post date:** [September 25, 2025, 2:01am UTC](https://community.seqera.io/t/wave-invalid-response-post-https-wave-seqera-io-v1alpha2-container-400-message-container-image-biocontainers-stringtie-2-2-3-h43eeafb-0-does-not-exist-or-access-is-not-authorized/2376/2 "2025-09-25T02:01:15Z")

</div>

> [@kokul-atx](#):
>
> `biocontainers/rseqc:5.0.3--py39hf95cd2a_0`

Hi Kokul,

do you specify [quay.io](http://quay.io) as the default docker.registry? Your error message only says biocontainers/rseqc:5.0.3–py39hf95cd2a\_0. If I try

```auto
docker pull biocontainers/rseqc:5.0.3--py39hf95cd2a_0

```

I also get an auth / access denied error. But when I try

```auto
docker pull quay.io/biocontainers/rseqc:5.0.3--py39hf95cd2a_0

```

The pull works succesfully. You might have to add [quay.io](http://quay.io) to the container image name or modify your default docker.registry if you are using that approach in your pipeline.

Hope that works!

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/system/32/2402_2.png) [@system](https://community.seqera.io/u/system)\
**Post date:** [October 7, 2025, 6:46pm UTC](https://community.seqera.io/t/wave-invalid-response-post-https-wave-seqera-io-v1alpha2-container-400-message-container-image-biocontainers-stringtie-2-2-3-h43eeafb-0-does-not-exist-or-access-is-not-authorized/2376/3 "2025-10-07T18:46:36Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.