Update image references to use fully qualified names. #2185
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
Signed-off-by: Hiroshi Hayakawa <hhiroshell@gmail.com>
…fully qualified names. Signed-off-by: Hiroshi Hayakawa <hhiroshell@gmail.com>
github-actions
bot
added
type/enhancement
hhiroshell
changed the title
2 tasks
Signed-off-by: Juan Bustamante <bustamantejj@gmail.com>
Signed-off-by: Juan Bustamante <bustamantejj@gmail.com>
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.
Summary
This PR updates references to container images to use fully qualified image names for improving Podman (and more) compatibility, addressing #1218 .
Output
N/A
Documentation
Since the pack's behavior will not change, there is nothing new to add to the documentation.
On the other hand, it is desirable that image names already written in documents, such as sample commands and builder names, be specified with the full name. It will be addressed with buildpacks/docs#702 .
Related
Resolves #1218