Added hints in errors message on possible causes of 403 status for docker push #1372
Conversation
This file contains hidden or 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
bhanurp
reviewed
Apr 9, 2025
bhanurp
requested changes
Apr 9, 2025
bhanurp
changed the title
bhanurp
reviewed
Apr 10, 2025
fluxxBot
force-pushed
the
dockerPushXray
branch
from
16009b2 to
a82f79e
Compare
bhanurp
approved these changes
Apr 10, 2025
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.
This change is done to address the issue where docker push command fails abruptly when a Xray policy in force (blocks any request on unscanned artifacts).
Below command is divided into two parts
jf docker push --build-name <name> --build-number <number>Docker push is successful but build info collection fails with 403 error while collecting docker image details when a Xray policy is in force. This PR aims to educate users with possible reasons for the failure since exact failure reason is not available as Head HTTP method is used to check image availability.