Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't pull images from dockerhub, missing manifests #7

Open
t0rrant opened this issue Apr 8, 2019 · 3 comments
Open

Can't pull images from dockerhub, missing manifests #7

t0rrant opened this issue Apr 8, 2019 · 3 comments

Comments

@t0rrant
Copy link

t0rrant commented Apr 8, 2019

From at least last Thursday I could no longer pull flowcraft images from the docker registry. The error states that there are missing manifests. Other images from the community or official images work fine in any of my setups.

Example

# for f in "${flowcraft[@]}"; do docker pull $f; done
Using default tag: latest
Error response from daemon: manifest for flowcraft/fastqc:latest not found
Using default tag: latest
Error response from daemon: manifest for flowcraft/trimmomatic:latest not found
Using default tag: latest
Error response from daemon: manifest for flowcraft/true_coverage:latest not found
Using default tag: latest
Error response from daemon: manifest for flowcraft/spades:latest not found
Using default tag: latest
Error response from daemon: manifest for flowcraft/bowtie2_samtools:latest not found
Using default tag: latest
Error response from daemon: manifest for flowcraft/pilon:latest not found

Versions

Shifter: 18.03.0
Docker: 18.09.2, build 6247962

@cimendes
Copy link
Member

Hello!

Sorry for the very late reply! I see that you're trying to pull the images using "latest" as tag (this is default docker behavior). In our docker hub repos we never use the latest tag, favoring instead to have the tool version and build as tag. For example, for SPAdes it should be docker pull flowcraft/spades:3.12.0-1

Can you confirm that when you correct the tag version you're able to successfully pull the image?

@t0rrant
Copy link
Author

t0rrant commented May 15, 2019

Hi @cimendes,

yes, when specifying a version it works. The idea behind not using the latest is due to different types of tests for each different version right?

@cimendes
Copy link
Member

Hello. It's a way to easily identify which software version corresponds to each container. For flowcraft we use these tags to keep track of the tool version implemented in each component.
A "latest" tag can could be added, with the most recent version of a container, but for the sake of reproducibility and validation, we avoid it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants