Fix glibc conflicts in containers #1194
Merged
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 patch series fixes issues with userland libraries that we normally build from sources, against a newer version of glibc, being exported into containers through the Jetson-specific passthrough mechanism. Such exports would result in mismatches with the glibc residing in the container, causing problems like gstreamer plugins failing to load.
The fix is to extend the container runtime's passthrough mechanism to look for exports in a separate subtree first, preferring exports from that tree over files that would normally be found in the normal place in the rootfs. The
tegra-container-passthrough
recipe is added to populate this tree with NVIDIA's prebuilt copies of libraries and plugins.The
l4t.csv
file is updated to refer to the files from their locations in the separate subtree (which uses the same Debian multiarch-style directory naming), and also has some missing entries restored. There are also some changes there to more accurately label symlinks vs. actual files, so the correct passthrough-mount method in the container runtime gets used.Fixes #857