grafeas / grafeas/voucher

Multi-arch image vouching fails: failed to load manifest with status 404 Not Found

Open
#47 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
75
Forks
19
PR merge metrics
No merged PRs in 30d

Description

I'm trying to vouch for a multi-arch image and getting this response:

```
failed to load manifest with status 404 Not Found:
"{"errors":[{
"code":"MANIFEST_UNKNOWN",
"message":"Manifest with digest 'sha256:XXX' has media type
'application/vnd.docker.distribution.manifest.list.v2+json',
but client accepts 'application/vnd.docker.distribution.manifest.v2+json,application/vnd.docker.distribution.manifest.v1+json,application/vnd.docker.distribution.manifest.v1+prettyjws'."}]}"
```

the request is:

```
http.post(
'https://voucher.acme.com/diy',
headers: {
'Authorization' => "Basic #{basic_authentication}",
'Content-Type' => 'application/json',
},
max_attempts: 4,
body: {
image_url: canonical_image_url,
}.to_json
```

and the manifest is:
```yml
{
"mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
"schemaVersion": 2,
"manifests": [
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"digest": "sha256:1512682275109406d73565ec11b8bd3aeaf53bfac83e8e12202a3effd0ae8ea4",
"size": 528,
"platform": {
"architecture": "arm",
"os": "linux",
"variant": "v7"
}
},
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"digest": "sha256:f587207cab008ab273d77a3b1c9f9c983888fa659a46e1284c1984272e4dc208",
"size": 528,
"platform": {
"architecture": "arm64",
"os": "linux"
}
},
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"digest": "sha256:fbb75455e35366f89fe310e88420a1a35a15ee54bc86aeef36fd561de68ce5ae",
"size": 528,
"platform": {
"architecture": "amd64",
"os": "linux"
}
}
]
}
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the /diy request loads and validates the Docker image manifest, using the reported manifest list media type and 404 response as the reproduction. Check how accepted manifest media types are selected, then verify that the supplied multi-arch image can be vouched successfully without the MANIFEST_UNKNOWN response.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.