median mirage
Hey All,
There seem to be a whole raft of modules which very much WIP, which is fine, they're easy enough to spot. But theres some that are broken, for example:
https://daggerverse.dev/mod/github.com/opopops/daggerverse/grype
Is there somewhere that we can report this so that they can be marked or removed?
left marsh
Hey! This is a good question. Overall daggerverse quality is an emerging topic.
One thing to note is that Daggerverse is a more of a search engine/index than a registry. It simply lists any public modules that exist in the world that we are able to find.
I think the best thing to do for a specific module is to file an issue on repo:
https://github.com/opopops/daggerverse/tree/327a52a86fa82c8a28102a10c27acac1525686a0/grype
Can you help me understand how this one is broken though?
lilac hornet
cc @polar bane @cedar tinsel @drifting jackal @rapid tendon good test case to watch for private daggerverse
(we need the capability to continuously check modules with a ratchet of dependency upgrades, and flag failures in the version matrix.
"dependency" can be a module or the engine itself
median mirage
Hey! This is a good question. Overall daggerverse quality is an emerging topic. ...
Hey Lev,
403 retrieving dependency:
! failed to create module: select: failed to update module dependencies: failed to initialize dependency modules: failed to initialize dependency module: select: failed to create module: select: failed to update codegen and runtime: failed to generate code: failed to call sdk module codegen: select: failed to resolve image "ghcr.io/astral-sh/uv:0.5.7@sha256:23272999edd22e78195509ea3fe380e7632ab39a4c69a340bedaba7555abe20a" (platform: "linux/arm64"): failed to resolve source metadata for ghcr.io/astral-sh/uv:0.5.7@sha256:23272999edd22e78195509ea3fe380e7632ab39a4c69a340bedaba7555abe20a: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Aastral-sh%2Fuv%3Apull&service=ghcr.io: 403 Forbidden
Thanks for the info @median mirage but I am not able to reproduce this, can you share more information about your environment or how you are triggering this error?
median mirage
I have no gcr config in docker, i had to reinstall docker the other day and it still doesnt work. So no idea.
"auths": {
"xxx-releases.io.xxx.com": {},
"xxxx.io.xxx.com": {},
"harbor.xxxxx.xxxx.com": {},
"https://index.docker.io/v1/": {}
},
"credsStore": "desktop",
Error: failed to generate code: input: moduleSource.withContextDirectory.withDependencies.asModule failed to create module: select: failed to update module dependencies: failed to initialize dependency modules: failed to initialize dependency module: select: failed to create module: select: failed to update codegen and runtime: failed to generate code: failed to call sdk module codegen: select: failed to resolve image "ghcr.io/astral-sh/uv:0.5.7@sha256:23272999edd22e78195509ea3fe380e7632ab39a4c69a340bedaba7555abe20a" (platform: "linux/arm64"): failed to resolve source metadata for ghcr.io/astral-sh/uv:0.5.7@sha256:23272999edd22e78195509ea3fe380e7632ab39a4c69a340bedaba7555abe20a: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Aastral-sh%2Fuv%3Apull&service=ghcr.io: 403 Forbidden
thanks for investigating but the repo owner couldnt replicate
could be that I have no gcr token configured, but if I need a gcr token then thats a bit eww.
rapid tendon
could be that I have no gcr token configured, but if I need a gcr token then tha...
no, that shouldn't have to be the case
could you rename your config.json to config.json.bkp for a bit and try again?
just want to check if it's rleated to that or not
median mirage
-rw-r--r--@ 1 krisjohnstone staff 78 16 Jan 10:37 config.json
-rw-r--r--@ 1 krisjohnstone staff 535 14 Jan 22:41 config.json.bkp
moved it, restarted docker
Error: failed to generate code: input: moduleSource.withContextDirectory.withDependencies.asModule failed to create module: select: failed to update module dependencies: failed to initialize dependency modules: failed to initialize dependency module: select: failed to create module: select: failed to update codegen and runtime: failed to generate code: failed to call sdk module codegen: select: failed to resolve image "ghcr.io/astral-sh/uv:0.5.7@sha256:23272999edd22e78195509ea3fe380e7632ab39a4c69a340bedaba7555abe20a" (platform: "linux/arm64"): failed to resolve source metadata for ghcr.io/astral-sh/uv:0.5.7@sha256:23272999edd22e78195509ea3fe380e7632ab39a4c69a340bedaba7555abe20a: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Aastral-sh%2Fuv%3Apull&service=ghcr.io: 403 Forbidden
@median mirage can you pull that astral-sh image via docker pull?
median mirage
docker pull ghcr.io/astral-sh/uv:0.5.7
Error response from daemon: Head "https://ghcr.io/v2/astral-sh/uv/manifests/0.5.7": denied: denied
I can write my own code to do grype scanning I was just hoping to save some time. And thought id ask re flagging the module as broken 🙂
left marsh
Thanks @median mirage - I appreciate you flagging this but it does not seem to be a global issue.
Here's what I see on my end
levlaz@Levs-MacBook-Air wrangler % docker pull ghcr.io/astral-sh/uv:0.5.7
0.5.7: Pulling from astral-sh/uv
08fa11bb38a2: Download complete
c0b9673d405f: Download complete
Digest: sha256:23272999edd22e78195509ea3fe380e7632ab39a4c69a340bedaba7555abe20a
Status: Downloaded newer image for ghcr.io/astral-sh/uv:0.5.7
ghcr.io/astral-sh/uv:0.5.7
Can you share any more info about your computer, OS, docker version, etc?
median mirage
I'm just about to get on a plane to Japan so will have to get the info, when i get back from holidays.
Its a Macbook Pro 2022 (M1)
its running Sequoia
but for actual build will need to get that when im back.
median mirage
Thanks <@400976074403610624> - I appreciate you flagging this but it does not se...
thats weird as.
Are you running ARM?
rapid tendon
Are you running ARM?
as @left marsh is saying, this issue seems to be related to some docker config on your end which is preventing you from pulling that particular image for some reason. Can you try pulling any other image from ghcr to see if that works?
For example, can you pull ghcr.io/dagger/engine:v0.15.2?
median mirage
as <@920499459484418068> is saying, this issue seems to be related to some docke...
docker pull ghcr.io/dagger/engine:v0.15.2
Error response from daemon: Head "https://ghcr.io/v2/dagger/engine/manifests/v0.15.2": denied: denied
turns out no
docker logout ghcr.io
and it works
I dont think I ever configured ghcr and certainly not since fresh install
rapid tendon
_I dont think I ever configured ghcr and certainly not since fresh install_
Lol, strange. Glad it worked