You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe the problem.
I've been investigating a few issues with other developers recently where the root cause was a different container image being used to what I expected. (See #7350 for more context)
Whilst the source column on the dashboard does list hte contaienr image used, this typically refers to a (potentially mutable) tag, which means there's opportunity for docker to think the tag means something other than a human user thinks
Describe the solution you'd like
I'd like to be able to see specifics about the specific base image being used
- Expose Digest of the image being used
- Expose Labels from the running image
- Expose `Created` date of the image from `docker image inspect`
Digest and Created date could be shown within resource details
Labels could also be shown within resource details, or could warrant their own heading on the resource details page.
A more extreme solution could also be to provide a UI that provides raw access to docker inspect:
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
I've been investigating a few issues with other developers recently where the root cause was a different container image being used to what I expected. (See #7350 for more context)
Whilst the source column on the dashboard does list hte contaienr image used, this typically refers to a (potentially mutable) tag, which means there's opportunity for docker to think the tag means something other than a human user thinks
Describe the solution you'd like
I'd like to be able to see specifics about the specific base image being used
Digest and Created date could be shown within resource details
Labels could also be shown within resource details, or could warrant their own heading on the resource details page.
A more extreme solution could also be to provide a UI that provides raw access to
docker inspect
:Additional context
No response
The text was updated successfully, but these errors were encountered: