When I try to pull, I’m getting this error
1 Like
I can replicate this problem
(note- moved some posts from a different thread into here so some things look out of order).
If i check the manifest of the GSA container i can see the linux/amd64:
Still getting “no matchin manifest…” error.
Thanks everyone for reporting this. 
The thread has been passed to the developers and they are looking into it.
3 Likes
Can also replicate this problem.
Will look into it. Thank you for your patience!
5 Likes
It’s working again. Thank you
3 Likes
Work again for me, thank you 
3 Likes
Thank you guys!
3 Likes
And thank you all for letting us know about it! 
2 Likes
I still received this error. cert-bund-data is causing it.
Also still have this issue.
<user>@<machine>:~/greenbone-community-container$ docker compose up -d
[+] Running 1/17
⠦ notus-data Pulling 0.6s
⠦ gvm-tools [⠀⠀⠀⠀⠀⠀⠀] Pulling 0.6s
⠦ ospd-openvas [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling 0.6s
⠦ pg-gvm Pulling 0.6s
⠦ configure-openvas Pulling 0.6s
⠦ vulnerability-tests [⠀⠀] Pulling 0.6s
⠦ dfn-cert-data [⠀⠀] Pulling 0.6s
⠦ openvas Pulling 0.6s
⠦ cert-bund-data Pulling 0.6s
⠦ data-objects [⠀⠀⠀] Pulling 0.6s
⠦ gvmd Pulling 0.6s
⠦ gpg-data [⠀⠀⠀] Pulling 0.6s
⠦ report-formats [⠀⠀⠀] Pulling 0.6s
⠦ redis-server [⠀⠀⠀] Pulling 0.6s
⠦ openvasd [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling 0.6s
⠦ gsa [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling 0.6s
⠦ scap-data [⣿⠀⣿] 1.982MB / 92.61MB Pulling 0.6s
no matching manifest for linux/amd64 in the manifest list entries
I still have the exact same Issue and still can’t get it to work, thank you for the support in advance
It’s working for me again, thank you
1 Like
Very cool. Please let us know if it happens again, thanks!
Thank you for your feedback, we are still looking for the problem, as it seems to be randomly appearing.
But it seems to work to rebuild the problematic images!
3 Likes
We (probably) identified the problem with the manifest(s) and are fixing the deployment pipeline - hopefully this issue is a problem of the past in future. 
2 Likes