You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
kchaung-lilly
changed the title
Parsing packing version numbers from container tag
Parsing package version numbers from container tag
Oct 23, 2024
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.
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!
The text was updated successfully, but these errors were encountered: