Conversation
Contributor
|
I am a bot, here is the pushed image/manifest for this PR:
|
Contributor
|
I am a bot, here is the pushed image/manifest for this PR:
|
aptalca
approved these changes
Mar 15, 2026
github-project-automation
bot
moved this from PRs Ready For Team Review
to PRs Approved
in Issue & PR Tracker
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description:
http2 frame size error is definitely a red herring caused by the way it handles connection upgrades, the real issue seems to be that we were setting HOME only for specific commands (and passing as the docker data dir) and buildx has changed something about how it handles that and dies, but only when trying to handle the container builder, and not the default docker one.
Benefits of this PR and context:
How Has This Been Tested?
Source / References: