<https://github.com/nf-core/modules/pull/9569> I w...
# wg-container-conversion-task-force
j
https://github.com/nf-core/modules/pull/9569 I would need to merge this to finish up the testing in my tools PR, do you think it's ok to merge?
👀 1
m
I'd say GO FOR IT
🚀 1
e
compared to this: https://nf-co.re/blog/2024/seqera-containers-part-2#changes-to-metayml singularity is missing the https:
j
ah right, do you know how to obtain this?
e
on seqera platform where I create containers, you just click the show https checkbox 😛
party this 1
m
you click on the get the httplink
if you don't have the build link anymore, you can reverse engineer it via the id
or asking for the same container/platform should do the trick
j
oh I was trying to use the command line 😄 is there a way to do it through the wave command? we would need this for the other tools commands
m
Oooh
there should be a way to get it
j
maybe someone else from <!subteam^S08LAB76NBU> knows? 👀
p
There is but it's faffy which is why I wrote a script for it. Didn't you take over this exact script the other week @Júlia Mir ? 😅
j
I tried but gave up 🙊 the script wasn't returning all the URLs, only docker. then discovered Julian and Yuxin had already done the work! only the https url is missing
To do it manually with the CLI:
Copy code
wave --inspect -o yaml -i <oras://community.wave.seqera.io/library/fastqc:0.12.1--104d26ddd9519960>
Untitled.yaml
j
thaaank you! keanu thanks
j
Sorry Julia, this was still missing from the new
modules container
functionality 😅 Is it safe to assume the url is always f"{hostName}/{imageName}/blobs/{digest}"? (instead of understanding what happens if we have many layers 🙈~)~
p
Singularity builds only ever have a single layer
Also I don't think it's safe to assume anything, better to use the API results directly
For example, last time I was using this, the URLs always had
/data
at the end, and apparently the one above does not.
So presumably something has changed there within the Wave build system
That, or I got something wrong.. 🤔
Searching FastQC on seqera.io/containers and doing Singularity + https gives this:
Copy code
<https://community-cr-prod.seqera.io/docker/registry/v2/blobs/sha256/e0/e0c976cb2eca5fee72618a581537a4f8ea42fcae24c9b201e2e0f764fd28648a/data>
Which does have the
/data
and looks kind of different.. So now, I'm not so sure about my CLI-foo 😅 Best to check the Python script which I took from the code we wrote for the Seqera Container website.
ahh no, the script just manually does some stuff to get the data URL, not just taking it directly:
Copy code
digest = layers[0]["digest"].replace("sha256:", "")
url = f"<https://community-cr-prod.seqera.io/docker/registry/v2/blobs/sha256/{digest[:2]}/{digest}/data>"
Hope that makes sense!
🙌 1