TurboOCI is reproducible for now, by removing unnecessary info from TurboOCI layer tar headers.
Support a new TurboOCI builder (called TurboOCI-meta-builder), which works with turboOCI-apply. This feature is still in the development stage, we plan to integrate it with the original TurboOCI-builder in the future.
Note: TurboOCI-meta-builder no longer uses an additional baselayer and will instead use mkfs, even if --mkfs is not specified.
Which issue(s) this PR fixes(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Please check the following list:
[ ] Does the affected code have corresponding tests, e.g. unit test, E2E test?
[ ] Does this change require a documentation update?
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[x] Do all new files have an appropriate license header?
What this PR does / why we need it:
Note: TurboOCI-meta-builder no longer uses an additional baselayer and will instead use mkfs, even if
--mkfsis not specified.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged): Fixes #Please check the following list: