Hi @jclausen I’m attempting to update our build to use the 3.8.0 Commandbox docker base image Checking https://hub.docker.com/layers/ortussolutions/commandbox/3.8.0/images/sha256-0dc072ec[…]b9964067b6ffc95b4e38daf954b332c4b0b425c8f801e?context=explore …I see this is actually a 6 year old image with CB 3.8.0, and not the latest image with CB 5.9.1 (that would have been an… interesting… build to run!!!) …and checking https://github.com/Ortus-Solutions/docker-commandbox/actions/runs/5893615671/job/15985529840 it seems this build process did not complete successfully. I can see the potential for issues, now that the docker image tag versions are running into the older commandbox tagged versions… not sure what can be done about that (other than a cleanup on the docker repo to remove the CB version tagged images from before when the docker images were tagged with a separate version)… In any case, would it be possible to resolve what is necessary to complete the 3.8.0 update build?

I noticed the same sort of thing yesterday, went to build with the “newest” tag and everything broke - assumed it might be a fully new version with commandbox 6 so backed out quickly…

Yeah - I always tend to check the layers within specific tag we are pulling to ensure that this matches expectations (especially for dependencies such as Java version, CB version etc.) - which tends to help avoid unexpected surprises 🙂

@danlance there used to be a time when the image version was the CommandBox version, but we changed that. I will have to look at why that tag didn’t get overwritten on the build. It looks like a couple of the tagged jobs in GitHub didn’t complete so I am rerunning the failed builds now. https://github.com/Ortus-Solutions/docker-commandbox/actions/runs/5893615671 When the build above finishes, that version should be overwritten.