fix: properly handle errors from ghcr.io #63
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smira
changed the title
frezbo
approved these changes
Nov 28, 2023
It returns 404 only when trying to pull a layer, but not when we get the manifest. Refactor all cases when we try to handle registry errors to use a common function. Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
smira
force-pushed
the
fix/registry-404
branch
from
28a4f80 to
f82ff73
Compare
|
Disabled govulncheck here using siderolabs/kres#330 |
|
Once the issue is resolved with |
|
/m |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It returns 404 only when trying to pull a layer, but not when we get the manifest.
Refactor all cases when we try to handle registry errors to use a common function.