fix: Use built-in image inspection for podman and docker #236
+143
−77
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
gmpinder
force-pushed
the
234-bug-unable-to-use-podman-as-the-inspect-driver
branch
2 times, most recently
from
29b18cd
to
0bec3f9
Compare
gmpinder
force-pushed
the
234-bug-unable-to-use-podman-as-the-inspect-driver
branch
from
0bec3f9
to
74fada1
Compare
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.
Ran into a situation where skopeo needs to be authenticated when inspecting images in a private registry. The
dockerandpodmanimplementations for the inspect driver should use the native way of inspecting. This has the downside that an image needs to be pulled before it can be inspected. With this change, usingskopeowill be the preferred way to inspect images as it does NOT require pulling images.