Allowable image signing on non paketo stacks #871
Merged
Conversation
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
If a build utilizing image signing is run on a stack with a different user than the completion image the container will not have access to the home directory. This allows the container to always have a writeable HOME directory which is the same as build-init.
matthewmcnew
force-pushed
the
allowable-image-signing-on-non-paketo-stacks
branch
from
f0b68eb
to
95a1534
Compare
tomkennedy513
approved these changes
Oct 25, 2021
dumez-k
approved these changes
Oct 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Mount the home volume in the completion container:
Prevent unnecessarily loading of credentials on builds that do not perform image signing.