-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support image registry mock server #425
Conversation
There are 20 test cases, failed count 0: See all test records
Reported by api-testing. |
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesCodacy will stop sending the deprecated coverage status from June 5th, 2024. Learn more |
There are 1 test cases, failed count 1:
See the error message* Case: CreateStore. error: literal not terminated (2:1) | /healthz", 2400) | ^. body:e2e-testing |
e1f803a
to
babd876
Compare
Quality Gate passedIssues Measures |
Now, it works well with docker client
I got these JSON data with docker image which was built by: FROM alpine:3.19.1 |
What type of PR is this?
What this PR does / why we need it:
I complete parts of the docker registry server. Users can run
docker pull
, but I cannot fix thefilesystem layer verification problem
. Please let me know if you are familiar with it.$ docker pull localhost:6060/linuxsuren/api-testing:master master: Pulling from linuxsuren/api-testing 56c566a8d234: Verifying Checksum filesystem layer verification failed for digest sha256:56c566a8d234cbea1867522f63b812f51bb091866286e8f350f23a951171b9f5
I have read the OCI Image Spec, but I still have no idea how to fix it. It looks like there are some problems on
Layer DiffID
.Which issue(s) this PR fixes:
Fixes #