build_sysext: Remove any opaque directory markers #1729
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.
The Flatcar extension images built with build_sysext created directories in the overlay in a way that masked contents from other layers. Instead of fixing the way we create directories, make use of postprocessing to avoid any similar problems show up again in the future.
How to use
Backport
Fixes flatcar/sysext-bakery#50
Testing done
Tested that the squashfs has no opaque markers:
Tested that the Azure OEM extension works with the Kubernetes extension such that
/usr/lib/systemd/system/multi-user.target.d
has the containerd and kubernetes entries.Jenkins: http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/3586/cldsv/