Inconsistent drydock container version displayed after update

[flederohr]

After automatic update of the drydock container Version: 1.5.0-rc.15 → 1.5.0-rc.17 I see inconsisten version information all over the drydock application.

In Container Overview the new Version 1.5.0-rc.17 is displayed

In the Environment tab i find the first inconsistency with DD_VERSION=1.5.0-rc.15

In the Labels tab org.opencontainers.image.version=1.5.0-rc.15

In the drydock Info: also version 1.5.0-rc.15

Here maybe the culprit in the Actions tab under the Update Operation History :

Update Operation History
3a3074e8-b5ea-46dc-ab4d-a9a2d81f5da0
failed
Phase: failed
Version: 1.5.0-rc.15 → 1.5.0-rc.17
Last error: Marked failed after orphaned active operation was found during process restart while in progress
5.5.2026, 10:14:46

[flederohr]

The version in the docker compose.yaml file is updated correctly

services:
  drydock:
    image: codeswhat/drydock:1.5.0-rc.17
    container_name: drydock
    restart: unless-stopped
    hostname: drydock
    group_add:
      - 1000
    labels:
      - dd.watch=true
      - dd.action.include=monitoring
      - dd.update.mode=infrastructure
      - dd.tag.include=^\d+\.\d+\.\d+(\-rc\.\d+)?$$
      - dd.tag.transform=^(\d+\.\d+\.\d+(\-rc\.\d+)?)$$ => $$1
    depends_on:
      - socket-proxy
 ...     

My assumtion is that the restart/upgrade of the docker compose is either not triggered or failed.

[flederohr]

Externally updating the docker compose.yaml with dockge results in a consistent state again, but the automatic update via drydock update mechanism fails the last step to trigger the actual update.

[s-b-e-n-s-o-n]

Thanks for the detailed report. I tracked this to Drydock’s self-update clone path preserving image-inherited env vars and OCI labels from the old container while switching to the new image. That left DD_VERSION and org.opencontainers.image.version pinned to the previous release even though the replacement container was using the newer image.

I’ve fixed the clone sanitization so stale image-inherited env vars and labels are dropped while operator-supplied values remain preserved, and added regression coverage for the self-update path. This is also noted in the unreleased changelog for the next rc.

[s-b-e-n-s-o-n]

Quick update: the fix for this is included in v1.5.0-rc.19 (just published at https://github.com/CodesWhat/drydock/releases/tag/v1.5.0-rc.19).

The self-update clone path now drops stale image-inherited env vars and OCI labels — so DD_VERSION, org.opencontainers.image.version, and the Info panel will all reflect the new image after a self-update completes cleanly. Operator-supplied env vars and labels remain preserved.

Could you upgrade to rc.19 and confirm the version display is consistent after the next self-update cycle? Happy to close this out once confirmed — thanks for the detailed screenshots that made the root cause obvious.

[flederohr]

Yes, i can confirm that after the update to version rc.19 the version display is consistent troughout the application.
I'm glad that you could sort this out.

[s-b-e-n-s-o-n]

Thanks for confirming! Closing this out — feel free to reopen or ping if anything regresses on a future RC.