Qiime2 installation via Docker container through singularity not working

Hello there!
I am typing because I was trying to retrieve the new Qiime2 version but brutally failed :sweat_smile:
I don't have Docker on my device, but I have singularity, therefore I go with:

singularity build qiime2_2023.9 docker://quay.io/qiime2/core:2023.9

It worked with 2023.2, but here instead it retrieves the following:

INFO: Starting build...
FATAL: While performing build: conveyor failed to get: reading manifest 2023.9 in Quay manifest unknown: manifest unknown

Can you help?
Thanks!

1 Like

Hi @AstroBioJack,
Docker Builds for 2023.9 will be up next week!

1 Like

Great @cherman2! Would you mind update this request here when it will happen? Thanks!!

1 Like

Hi @AstroBioJack,

Please keep an eye on our release changelog for 2023.9 - we will provide an update there once the latest Docker image is available!

Cheers :lizard:

1 Like

Good afternoon!

Although my setup may be different, I just ran into the same error.

Pulling singularity image docker://quay.io/qiime2/core:2023.9.
WorkflowError:
Failed to pull singularity image from docker://quay.io/qiime2/core:2023.9:
FATAL:   While making image from oci registry: error fetching image to cache: failed to get checksum for docker://quay.io/qiime2/core:2023.9: reading manifest 2023.9 in quay.io/qiime2/core: manifest unknown: manifest unknown

I wonder if this is an issue with Snakemake and Quary.io?
(The snakemake examples use Docker Hub)

    container:
        "docker://quay.io/qiime2/core:2023.9"

EDIT: It looks like this may be working with docker://quay.io/qiime2/core:2023.7.
I wonder if something happened when Distributions were introduced?

Hey @colinbrislawn!

This is actually perfect timing - I just built the new Docker image at the end of last week, and updated our Docker instructions as of this morning!

The reason your command isn't working is because we've replaced core with amplicon in the image name. Here are our updated install instructions (which I'll also post on the release changelog in just a few mins):
https://docs.qiime2.org/2023.9/install/virtual/docker/

But this should resolve the issue - let me know if you run into any other hiccups though!

Cheers :lizard:

1 Like

Hey @lizgehret ,
I tried a few minutes ago to build the container with the updated instruction from :qiime2: docs, but I retrieve the following error:

singularity build qiime2_2023.9 docker://quay.io/qiime2/amplicon:2023.9
INFO: Starting build...
FATAL: While performing build: conveyor failed to get: reading manifest 2023.9 in quay.io/qiime2/amplicon: unauthorized: access to the requested resource is not authorized

Can you help?
Thanks!

1 Like

Hi,

I see this issue has been assigned, so I guess it will be solved. Just a comment that I experience the same. I guess the image has not been made public yet, since I also can't access the overview page: Quay

I would actually opt for naming the image qiime2. This would enhance visibility. Currently it does not show up in the quay search if you use 'qiime', only 'core' works: Quay

2 Likes

Hello all!

Thanks for your patience - the latest images should now be publicly available, sorry about that! Creating a new repository for amplicon (formerly core) defaults to private, but since the image was cached on my machine, I was able to use it without any issues. In any case, this repository has been set to public and pulling the latest images have been tested on a separate machine successfully.

@mdehollander thanks for the suggestion! Since we have different distributions of QIIME 2, we do need to maintain different repository names. Most of our users go through the user documentation for Docker install instructions, which do list the image name(s) - so we will most likely keep things as they are for the time being.

Cheers :lizard:

1 Like

Thank you @lizgehret, I can confirm installation worked for me :slight_smile:

2 Likes

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