Suggestion - Show version of current and discovered containers #159

Activity

1. mag37 commented on Apr 10, 2025

   

   mag37

   on Apr 10, 2025

   Last edited by mag37

   Owner

   More actions

   It's not really possible due to a few reasons.
   The check for new updates is done on the hash of the image. It checks the latest image (with the same version tag) available and compares it to the local image.
   Like this with the image amir20/dozzle:latest:

   # first checking the local image:
   docker image inspect amir20/dozzle:latest --format='{{.RepoDigests}}'
   [amir20/dozzle@sha256:ed6e585340cc9ad723356e9b2633473114bca52c43243a1044aaa005f6bee6ed]
   
   # then the one in the registry:
   regctl -v error image digest --list amir20/dozzle:latest
   sha256:7a1144f8e74bf07a23971c19280ebb209c6c8d8cf04feab28409868e946622fd
   
   # then there's some logic to compare the hashes
   # local:
   ed6e585340cc9ad723356e9b2633473114bca52c43243a1044aaa005f6bee6ed
   # registry:
   7a1144f8e74bf07a23971c19280ebb209c6c8d8cf04feab28409868e946622fd

   As they're not the same - there's an update available.
   That update can be anything from one typo fixed to a complete rewrite of the application.

   The versioning of images is all up to the creator - so it's very hard to build a generalized and consistent way of comparing or reporting on differences.

   One creator might only have a v1 - building on that for ages with fixes and updates released and then releases a v2 when they do something huge. Another one might have a v0.1.3.b and change their versions on every small change.
   Another one might not have version numbers at all - just a main that gets updated all the time without release-numbering.

   So this is somewhat up to the user - if you've got an important application you should use a version tag to the image, then manually read up on moving to the next one. Like Nextcloud or Immich - might change things and warns about breakage in their releases - then you'd pin that to a specific version which is granular - lets say they have a v1.3.5 then you can pin it to :1.3.5 and it will stay on that and get updates/fixes the creator sticks to that tag, or pin it to :1 and it will update within the v1 but not move to v2.

   There's some work to list release note URLs alongside the list of containers with updates, will release it today most likely.
   It's currently in this branch https://github.com/mag37/dockcheck/tree/styleAndAdditions

   But that's the best I can do right now I'm afraid.
2. mag37

   added

   wontfixThis will not be worked onThis will not be worked on

   on Apr 12, 2025
3. mag37 commented on Apr 14, 2025

   

   mag37

   on Apr 14, 2025

   Owner

   More actions

   I currently wont pursue this - so I'll close it for now.
   Maybe in the future I'll look a tags again.

   👍React with 👍1Reacted by thewonderer73
4. mag37

   closed this as completedon Apr 14, 2025
5. evrial commented on Jul 14, 2025

   

   evrial

   on Jul 14, 2025

   More actions

   You can use cup

   cup check
   ✓ Done!
   ~ Local images
    ╭──────────────────────────────────────────────────────────────┬──────────────────────┬─────────╮
    │Reference                                                     │Status                │Time (ms)│
    ├──────────────────────────────────────────────────────────────┼──────────────────────┼─────────┤
    │postgres:14-alpine                                            │Major update (14 → 17)│426      │
    │redis:7-alpine                                                │Major update (7 → 8)  │406      │
    │amir20/dozzle:latest                                          │Up to date            │411      │
   

   👍React with 👍1Reacted by Robin Ivehult