-
Notifications
You must be signed in to change notification settings - Fork 632
driver/docker-container: remove uses of jsonmessage #3777
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
Draft
thaJeztah
wants to merge
1
commit into
docker:master
Choose a base branch
from
thaJeztah:no_jsonmessage
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1
−249
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
245 changes: 0 additions & 245 deletions
245
vendor/github.com/moby/moby/client/pkg/jsonmessage/jsonmessage.go
This file was deleted.
Oops, something went wrong.
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
Oops, something went wrong.
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.
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.
#2988 changed this code path to explicitly read the pull JSON stream and return any
errorDetailentries from the daemon.That behavior matters because images/create can return 200 OK and then report the real failure later in the streamed JSON response, which is the bug fixed in moby/moby#49453
The current implementation still preserves that because DisplayJSONMessagesStream() returns jm.Error from the stream:
buildx/vendor/github.com/moby/moby/client/pkg/jsonmessage/jsonmessage.go
Lines 116 to 144 in 182f1f4
buildx/vendor/github.com/moby/moby/client/pkg/jsonmessage/jsonmessage.go
Lines 186 to 200 in 182f1f4
By contrast, resp.Wait(ctx) only returns decoder/context errors and does not inspect jsonstream.Message.Error at all:
buildx/vendor/github.com/moby/moby/client/internal/jsonmessages.go
Lines 47 to 83 in 182f1f4
buildx/vendor/github.com/moby/moby/api/types/jsonstream/message.go
Lines 8 to 14 in 182f1f4
So this change looks like a regression of #2988: pull failures reported via streamed
errorDetailwould be silently ignored again, and bootstrap would fall through to a later, less accurate error.