Don't use container runtimes bundled with podman-static release #7352
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 PR should fix the memory corruption bug ("corrupted size vs. prev_size") mentioned in https://github.com/buildbuddy-io/buildbuddy-internal/issues/3631
It turns out that
podman-static
includes its own versions ofcrun
andrunc
under/usr/local/bin
, which has higher precedence in PATH than the ones we provision under /usr/bin. So when upgrading to the latestpodman-static
release, we inadvertently upgradedcrun
to version 1.16.1, which has a double-free bug. This was causing the "corrupted size vs. prev_size" errors we were seeing in some teed actions.The double-free bug won't be fixed until 1.16.2, so this PR effectively just downgrades us to 1.15 until 1.16.2 is available.
Related issues: https://github.com/buildbuddy-io/buildbuddy-internal/issues/3631