Create separate page to show container image tag details

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

We propose creating a separate page to show detailed information for individual container image tags. This enhancement is based on the discussion about improving the representation of tag-related information.

Value of Displaying Additional Metadata

1. Comprehensive Information: A dedicated page for tag details allows us to present a more comprehensive set of metadata, providing users with a deeper understanding of each container image tag.
2. Improved User Experience: By moving detailed information to a separate page, we can maintain a clean and uncluttered tags list page while still offering in-depth information when needed.
3. Support for Multi-arch Tags: This approach would be particularly beneficial for multi-arch index tags, allowing users to easily view and compare information across different architectures.
4. Enhanced Visibility of Critical Metadata: We can prominently display important information such as:
   • Target OS/architecture
   • Manifest details (along with ability to view raw manifest)
   • Configuration payloads
   • Build information
   • Security scan results
   • Image size and layer information
   • Docker labels
5. Facilitating Decision Making: With more detailed metadata readily available, users can make more informed decisions about which tags to use for their specific use cases.
6. Improved Troubleshooting: Detailed metadata can aid in troubleshooting issues related to specific image tags, potentially reducing the time and effort required to resolve problems.
7. Version Comparison: A dedicated page could allow for easier comparison between different versions of the same image, helping users understand changes and updates.
8. Docker Labels: Displaying Docker labels provides crucial information about the image, such as maintainer details, version information, licensing, and custom metadata added by the image creator. This can help users better understand the image's purpose, origin, and any special instructions or requirements.

Questions to Consider

• How can we ensure that the new page integrates smoothly with existing workflows and doesn't introduce unnecessary complexity?
• Should we consider adding any interactive elements to the page, such as the ability to compare tags or visualize differences?
• How should we handle and display Docker labels, especially for images with a large number of custom labels?