Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Write buildpack directories to builder layer
When a custom buildpack is provided for image building, the contents of the buildpack directory, tgz file, or image are copied as tar entries to a new layer in the ephemeral builder image. Prior to this commit, only file entries from the buildpack source were copied as builder layer tar entries; intermediate directory entries from the source were not copied. This results in directories being created in the builder container using default permissions. This worked on most Linux-like OSs where the default permissions allow others-read access. On some OSs like Arch Linux where the default directory permissions do not allow others-read, this prevented the lifecycle processes from reading the buildpack files. This commit explicitly creates all intermediate directory tar entries in the builder image layer to ensure that the buildpack directories and files can be read by the lifecycle processes. Fixes gh-26658
- Loading branch information
1 parent
e2cba40
commit f560e86
Showing
11 changed files
with
171 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.