"latest" tag and revision tag (e.g. 6.7-noble-r0) were not created on Docker Hub for 6.7 app image

[pdurbin]

If end users try the quickstart at https://guides.dataverse.org/en/6.7/container/running/demo.html#quickstart they'll get an error like this:

% docker compose up
WARN[0000] The "STORAGE_DIR" variable is not set. Defaulting to a blank string. 
WARN[0000] /Users/PDurbin/github/iqss/dataverse/docker/compose/demo/compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
[+] Running 4/4
 ✘ dv_initializer Error   context canceled                                                                           3.1s 
 ✘ solr_initializer Error context canceled                                                                           3.1s 
 ✘ dataverse Error        failed to resolve reference "docker.io/gdcc/dataverse:latest": docker....                  3.1s 
 ✘ bootstrap Error        context canceled                                                                           3.1s 
Error response from daemon: failed to resolve reference "docker.io/gdcc/dataverse:latest": docker.io/gdcc/dataverse:latest: not found

This is because (as the error says), the "latest" tag was not pushed to https://hub.docker.com/r/gdcc/dataverse/tags during the 6.7 release.

The revision tag (e.g. 6.7-noble-r0) wasn't pushed either.

@poikilotherm and I are discussing this in Zulip: https://dataverse.zulipchat.com/#narrow/channel/375812-containers/topic/6.2E7.20release/near/529892680

Related:

• 6.7 app image tag wasn't created on release #11659
• Fix ct image releasing #11660
• "latest" tag was not created on Docker Hub for 6.7 base image #11662

[pdurbin]

If end users try the quickstart at https://guides.dataverse.org/en/6.7/container/running/demo.html#quickstart they'll get an error like this:

Until we push the "latest" tag to Docker Hub, a workaround is to edit the compose.yml file and use the "6.7-noble" tag like this:

% diff -u compose.yml.orig compose.yml
--- compose.yml.orig	2025-07-23 16:01:42
+++ compose.yml	2025-07-23 16:02:21
@@ -5,7 +5,7 @@
   dataverse:
     container_name: "dataverse"
     hostname: dataverse
-    image: gdcc/dataverse:latest
+    image: gdcc/dataverse:6.7-noble
     restart: on-failure
     user: payara
     environment:

[poikilotherm]

I have the explanation for why this doesn't work for gdcc/dataverse, but it does for gdcc/base and gdcc/configbaker. It's hard to spot! For the application image we have an definition, pointing to our Docker Compose file. Using properties to override the tags settings usually requires to use such an configuration, but with properties. So we basically cannot combine both at the moment.

I created an issue with the DMP folks:

• Using external compose file, I cannot add custom image tags using Maven properties fabric8io/docker-maven-plugin#1883

[poikilotherm]

In case we don't find a good solution within the DMP, the alternative plan is to add the tags on the fly to the Docker Compose or Maven POM from within the maintain-application.sh script. As these files are checked out from the repos anyway, we can edit away without breaking anything.