oasisprotocol / oasisprotocol/cli
ROFL build doesn’t catch missing amd64/Linux image
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 80
- Forks
- 23
- Avg merge
- 9h 43m
- Merged PRs (30d)
- 3
Description
I ran into this:
{"level":"info","module":"runtime/global","msg":"Trying to pull docker.io/ptrusr/trustless-x402-facilitator:latest...","ts":"2025-12-05T11:28:40.229691244Z"}
{"level":"info","module":"runtime/global","msg":"Error: choosing an image from manifest list docker://ptrusr/trustless-x402-facilitator:latest: no image found in image index for architecture \"amd64\", variant \"\", OS \"linux\"","ts":"2025-12-05T11:28:40.902055786Z"}
I thought we would catch this during the ROFL build/validation steps, but apparently we don’t. We should detect missing arch/OS entries earlier instead of failing at runtime.
I think we also saw this issue on the BA hackathon.
I haven’t investigated further yet.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the ROFL build and validation path that handles Docker image manifests, then reproduce the reported case with an image missing a linux/amd64 entry. Done means the build or validation step reports the missing architecture/OS entry before runtime; the issue names no specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100