Document referring to container images by their hash instead of their #21
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
name, as an alternative to the tag system. Minor updates to asciidoctor-spec image to work with the current REUSE and update the Node.js version to current (18).
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.
name, as an alternative to the tag system.
Minor updates to asciidoctor-spec image to work with the current REUSE
and update the Node.js version to current (18).
@rpavlik this may be of interest to you - someone on my Facebook (?! :-)) suggested using hashes and I think that's preferable for the Vulkan CI. The trick for determining the hash came from
https://stackoverflow.com/questions/32046334/where-can-i-find-the-sha256-code-of-a-docker-image?noredirect=1&lq=1