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

Parsing package version numbers from container tag #716

Open
kchaung-lilly opened this issue Oct 23, 2024 · 3 comments
Open

Parsing package version numbers from container tag #716

kchaung-lilly opened this issue Oct 23, 2024 · 3 comments

Comments

@kchaung-lilly
Copy link

Hello, in our group, we have users building many similar Wave containers. However, the package versions are no longer in the container names, and it is difficult to see what's inside without entering and inspecting.

Is there any way to parse the package version names from the tag hash?
For example, in community.wave.seqera.io/library/bbmap_pigz_seqkit_csvtk:fa8c3b82bba97878, can fa8c3b82bba97878 be used to determine what are the versions of bbmap, pigz, seqkit, and csvtk?

Thank you!

@kchaung-lilly kchaung-lilly changed the title Parsing packing version numbers from container tag Parsing package version numbers from container tag Oct 23, 2024
@pditommaso
Copy link
Collaborator

Yes, you can use this uri https://wave.seqera.io/view/builds/{id} for example https://wave.seqera.io/view/builds/fa8c3b82bba97878

@kchaung-lilly
Copy link
Author

Thanks!

I specifically was referring to the use case of when we have already pushed a copy of the container into our ECR, so the container name may look like <AWS_ENV>/wave/containers/bbmap_pigz_seqkit_csvtk:fa8c3b82bba97878. At this point, we may no longer be able to retrieve the build id.

@pditommaso
Copy link
Collaborator

wave strips the version numbers from the tag when there's more than one tools because it could be quire unreadable.

An option could be include in the image name, but not sure how much it will improve the problem

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