Always update the ldcache in the container #1326
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.
Even though a particular image (distroless, busybox, alpine) doesn't include ldconfig, a user may include tooling to read the ldcache in the container or applications may process the ldcache using dlopen.
This change always creates the /etc/ld.cache file in the container to ensure that this works as expected.
This effectively reverses the changes made in https://gitlab.com/nvidia/container-toolkit/container-toolkit/-/merge_requests/369. Here the actual cause of failures in containers that don't use the ldcache was the missing
/etc/ld.so.conf.dfolder and not the ldcache itself.