[release-1.42] Run: don't try to encode SystemContext with json#6665
Merged
Luap99 merged 1 commit intocontainers:release-1.42from Feb 5, 2026
Merged
Conversation
Don't expect to be able to encode a SystemContext as JSON, because it will trigger an encoding error if fields which can't be encoded are set. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
dosubot
bot
added
the
size:XS
|
Ephemeral COPR build failed. @containers/packit-build please check. |
2 similar comments
|
Ephemeral COPR build failed. @containers/packit-build please check. |
|
Ephemeral COPR build failed. @containers/packit-build please check. |
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
2 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.
What type of PR is this?
/kind other
What this PR does / why we need it:
Don't expect to be able to encode a
SystemContextas JSON, because it will trigger an encoding error if fields which can't be encoded are set.How to verify it
podman has a "podman build - basic test" test that should be fixed by this.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Cherry-picked from #6650
Does this PR introduce a user-facing change?