I think it has to do with whether or not the image contains enough metadata for a scan to take place and thus it doesn't know the status of said image. I'm going out on a limb, but this would be something the dev team should have included in his manifest or what ever(?). I'm not a Docker programmer. I think I read that somewhere else. Give corrections if any.
5 Comments
just_another_person@lemmy.world · 18 pts · 206d
Because you're being rate limited. Don't let these tools constantly hammer Github's API in mass fits and starts or you may get a back off from GH.
frongt@lemmy.zip · 9 pts · 206d
What does the log say?
gratux@lemmy.blahaj.zone · 7 pts · 206d
Just a wild guess, but maybe it got rate limited by GitHub?
blarg_dunsen@sh.itjust.works · 1 pts · 206d
Also manually verify your access tokens, even with PATs their interface is really janky and some repos might have weird permissions.
irmadlad@lemmy.world · 0 pts · 206d
I think it has to do with whether or not the image contains enough metadata for a scan to take place and thus it doesn't know the status of said image. I'm going out on a limb, but this would be something the dev team should have included in his manifest or what ever(?). I'm not a Docker programmer. I think I read that somewhere else. Give corrections if any.gratux@lemmy.blahaj.zone · 0 pts · 206d