-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REST API Method Not Allowed with Podman 2.0.5 and Grype #7950
Comments
Ok, dug into this a little. The problem is that they are hitting an endpoint that doesnt exist because we were not able to save/load multiple images in a single tarball. I think @vrothberg worked on this recently. @vrothberg lets talk about this one, coach me up if we can do this. |
The loading part is working transparently (https://github.com/containers/podman/blob/master/libpod/runtime_img.go#L279) as we are trying a couple of formats in a specific order. The saving part, however, needs to know whether we are creating a multi-image archive or a single-image archive with additional tags. On the CLI, we added the |
with the recent inclusion of dealing with multiple images in a tar archive, we can now add a compatibility endpoint that was missing images/get?names=one,two. Fixes: containers#7950 Signed-off-by: baude <[email protected]>
/kind bug
Description
Using Grype (https://toolbox.anchore.io/) with CentOS Stream 8 and Podman 2.0.5, the Docker Compatible REST endpoint returns a Method not Found error.
Steps to reproduce the issue:
1.grype registry.access.redhat.com/ubi8/ubi
Or
Describe the results you received:
From terminal:
From debug log:
Describe the results you expected:
Results similar to video here: https://toolbox.anchore.io/
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
No
Additional environment details (AWS, VirtualBox, physical, etc.):
Virtual machine with CentOS 8 Stream. I suspect that this could be as simple as accepting 1.40 as the version number?
The text was updated successfully, but these errors were encountered: