-
Notifications
You must be signed in to change notification settings - Fork 63
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
Fix pulling from nvcr.io #285
base: master
Are you sure you want to change the base?
Conversation
Nikita, The latest updates added an option to use some external tools from the broader OCI community to handle pulling and unpacking images. This may be a more robust way to deal with these other repositories. But I'll take a look at the PR. |
# The json content type can include a extra bit defining the character set | ||
# so we just check the beginning. Worst case is the json.loads will throw | ||
# an error just after this. | ||
if not resp.getheader('content-type').startswith('application/json'): |
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.
Why was this dropped? Does the nvcr case not return json?
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.
This part is from your original PR, but I can check if it's still needed.
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.
This looks good as far as I can tell. I would like to run it and make sure there aren't any edge cases that fail.
Sounds good! Is there something I should do to enable this new pulling method? |
Here is the documentation on the external mode option.... |
Based on #238 with my suggestions applied.