docker-library / docker-library/mongo
Manifest size validation failure on mongo:8.3-noble
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 658
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
Description
Hi,
Yesterday, version 8.3.11 of MongoDB was released on Docker Hub.
When I tried to download the new version using the tag
mongo:8.3-noble
in my Dockerfile, BuildKit returned this error:
error: failed to solve: mongo:8.3-noble: failed to resolve source metadata for docker.io/library/mongo:8.3-noble: failed commit on ref "index-sha256:02eb14a1130c6d060847c4169eccd4d79d9f172a584da7aea8f160c492537b02": "index-sha256:02eb14a1130c6d060847c4169eccd4d79d9f172a584da7aea8f160c492537b02" failed size validation: 2605 != 2603: failed precondition
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
The report names a Dockerfile and the mongo:8.3-noble tag, but no repository file or test. Start by reproducing the BuildKit pull and inspect the image manifest metadata; the issue is done when the tag resolves without the reported size-validation failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mongodb
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100