Enables directory-buildpack support for WCOW/LCOW #1157
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.
pack build ... --buildpack <directory>
andpack builder create ...
withbuilder.toml
containing buildpacks with directories.Signed-off-by: Micah Young ymicah@vmware.com
Summary
This removes the guard disabling directory buildpacks on LCOW/WCOW. Directory-based buildpacks can now be used for builders and within apps with appropriate project.toml. Test coverage that previously only ran on Linux, now also runs on Windows (LCOW & WCOW).
Output
Before
After
The images generated are equivalent to current sample images in terms of the relevant buildpack files. The image IDs are different due to unrelated metadata causing slightly different image digests.
This example generates tarball saves of sample builders and compares the tarball entries using gnu-tar verbose output:
nanoserver sample builder on Windows host with local WCOW daemon
alpine sample builder on Windows host with local LCOW daemon
compare builder image tarballs in POSIX environment (for gnu-tar) containing copied tarballs:
Documentation
The only needed change I could find would be to remove this line:
https://github.com/buildpacks/docs/blame/71f3b301ad809341b0e84e9363a4024694b9eb65/content/docs/app-developer-guide/specific-buildpacks.md#L104
Other existing documentation and walkthroughs accurately describing the behavior.
Related
Resolves: N/A no existing issue