Containers Page: Separate Column for Version Tag and Software/Container Version?

[begunfx]

Please see screenshot. Column for version only shows the version tag. Would be really helpful if we had that column named something like "Tag" and an additional column added that is "Version" that shows the version of the running container.

[scttbnsn]

Good idea — this is something I've been thinking about since the floating tag work landed in v1.5.

What exists today

Drydock currently conflates the image tag and the software version into a single value. The dd.inspect.tag.path label lets you extract a version from the container's Docker inspect metadata (e.g., Config/Labels/org.opencontainers.image.version), but it replaces the image tag rather than showing both side by side. So you get one or the other — not both.

What would make this work well

Many images already publish their software version via the OCI standard label org.opencontainers.image.version. Drydock could read this automatically from the image inspect data without requiring any user-side labels.

The approach I'm thinking about:

1. Automatically extract org.opencontainers.image.version from inspect data when available (no label needed)
2. Keep both values — the image tag stays in its current field, the software version goes in a new image.softwareVersion field
3. UI shows both — rename the current column to "Tag" and add a "Version" column (or show version as a secondary line under the tag when present)
4. dd.inspect.tag.path still works — but now stores the extracted value in the software version field instead of overwriting the tag

This would also pair nicely with the floating tag detection — a container running latest (floating) with org.opencontainers.image.version: 2.3.4 would show both pieces of information, which is exactly the case where knowing the actual version matters most.

I'll add this to the v1.6 plan.

[scttbnsn]

This is queued for v1.6.0 (Phase 5.7).

The plan is to automatically extract org.opencontainers.image.version from image inspect data, keep the image tag in its current field, and add a dedicated "Version" column alongside it — no user-side labels needed for images that ship the OCI standard label. The existing dd.inspect.tag.path label will also be updated to populate the version field instead of overwriting the tag, so both values are always visible.

This pairs particularly well with floating-tag containers (latest) where knowing the actual running software version matters most.

[scttbnsn]

Scheduled for v1.6.0. We'll split the conflated column into a separate Tag column and a Version column, auto-extracting the software version from the OCI org.opencontainers.image.version label where images publish it (falling back to the tag when they don't). I'll update this thread when it's in a release.

[scttbnsn]

Quick update — this is shipping in v1.5.1-rc.4, earlier than the v1.6 I'd mentioned.

The containers table now has a separate Tag column (the image tag, like before) and a new Version column showing the application version baked into the image — read from the org.opencontainers.image.version OCI label, falling back to the running container's inspect metadata. The same software version also shows in the side panel and the full-page detail view.

Important: this is non-breaking. dd.inspect.tag.path works exactly as it did — it still overwrites the tag for update detection by default, and now also populates the new Version column. If you'd rather keep the real image tag untouched and route the inspect value to the Version column only, set dd.inspect.tag.version-only=true on the container.

Give it a try once rc.4 is out and let me know if the columns show what you expected.