-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
include arch/os in image libpod list #22185
Comments
@vrothberg PTAL, I think the problem here is that libimage does not return these by default but only in inspectinfo. Valentin would their be a penalty to return these automatically in list? |
Yes, this information comes at some cost. In theory, Podman Desktop could get this information in two steps:
It could certainly be made part of PS: I have no time to implement this feature at the moment. |
i have the ball on this one. |
when listing images through the restful service, consumers want to know if the image they are listing is a manifest or not because the libpod endpoint returns both images and manifest lists. in addition, we now add `arch` and `os` as fields in the libpod endpoint for image listing as well. Fixes: containers#22184 Fixes: containers#22185 Signed-off-by: Brent Baude <bbaude@redhat.com>
when listing images through the restful service, consumers want to know if the image they are listing is a manifest or not because the libpod endpoint returns both images and manifest lists. in addition, we now add `arch` and `os` as fields in the libpod endpoint for image listing as well. Fixes: containers#22184 Fixes: containers#22185 Signed-off-by: Brent Baude <bbaude@redhat.com>
when listing images through the restful service, consumers want to know if the image they are listing is a manifest or not because the libpod endpoint returns both images and manifest lists. in addition, we now add `arch` and `os` as fields in the libpod endpoint for image listing as well. Fixes: containers#22184 Fixes: containers#22185 Signed-off-by: Brent Baude <bbaude@redhat.com>
when listing images through the restful service, consumers want to know if the image they are listing is a manifest or not because the libpod endpoint returns both images and manifest lists. in addition, we now add `arch` and `os` as fields in the libpod endpoint for image listing as well. Fixes: containers#22184 Fixes: containers#22185 Signed-off-by: Brent Baude <bbaude@redhat.com>
when listing images through the restful service, consumers want to know if the image they are listing is a manifest or not because the libpod endpoint returns both images and manifest lists. in addition, we now add `arch` and `os` as fields in the libpod endpoint for image listing as well. Fixes: containers#22184 Fixes: containers#22185 Signed-off-by: Brent Baude <bbaude@redhat.com>
when listing images through the restful service, consumers want to know if the image they are listing is a manifest or not because the libpod endpoint returns both images and manifest lists. in addition, we now add `arch` and `os` as fields in the libpod endpoint for image listing as well. Fixes: containers#22184 Fixes: containers#22185 Signed-off-by: Brent Baude <bbaude@redhat.com>
when listing images through the restful service, consumers want to know if the image they are listing is a manifest or not because the libpod endpoint returns both images and manifest lists. in addition, we now add `arch` and `os` as fields in the libpod endpoint for image listing as well. Fixes: containers#22184 Fixes: containers#22185 Signed-off-by: Brent Baude <bbaude@redhat.com>
Feature request description
Today,
are only available when we inspect an image
But usually this information is useful when we want to list images. For example to know if an image is using
amd64
or Apple Silicon computer, etc.so it requires one additional query for each image.
Suggest potential solution
Include
as part of
libpod/images/json
return this informationcould be with an additional query parameter to the endpoint
?arch=true&os=true
,?displayArchAndOs
, whatever so opt-in query.Have you considered any alternatives?
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: