-
Notifications
You must be signed in to change notification settings - Fork 205
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
Nydusify: fix some bug about the subcommand mount of nydusify #1328
Conversation
- The `nydusify mount` subcomend don't require `--backend-type` and `--backend-config` options when the backend is registry. - The methord to resolve it is we can get the `--backend-type` and `--backend-config` options from the docker configuration. - Also, we have refractor the code of checker module in order to reuse the code Signed-off-by: lihuahua123 <[email protected]>
@lihuahua123 , a new test job has been submitted. Please wait in patience. The test job url: https://tone.openanolis.cn/ws/nrh4nnio/test_result/79034 |
@lihuahua123 , The CI test is completed, please check result:
Congratulations, your test job passed! |
@lihuahua123 , the title has been updated, so a new test job has been submitted. Please wait in patience. The test job url: https://tone.openanolis.cn/ws/nrh4nnio/test_result/79067 |
@lihuahua123 , The CI test is completed, please check result:
Congratulations, your test job passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Relevant Issue (if applicable)
this is the solution of issue #1306
Details
we fix the bug, the nydusify
mount
subcommand will not need the--backend-type
and--backend-config
options when the blobs of target image are all stored in the registry,Types of changes
Checklist