@ericvaandering Looking at both Dockerfiles, it looks like each of them refer to different trace source repos:

CMSRucio (https://github.com/dmwm/CMSRucio/blob/master/docker/rucio-tracer/Dockerfile)

• Valentin's repository, https://github.com/vkuznet/RucioTraces
• Last updated 2 years ago

dmwm/rucio-tracers

• https://github.com/dmwm/rucio-tracers
• Last updated 3 years ago

Which repository should we be building from?

Looking in dmwm/rucio-flux (https://github.com/dmwm/rucio-flux/tree/main/apps/base/cms-rucio-traces), we are using https://hub.docker.com/r/cmssw/rucio-tracers/tags at version 4.0.5.

I think the https://github.com/dmwm/rucio-tracers repo has a release version 4.0.5, so it is potentially this image we are using.

Simultaneously with this issue, we might want to consider moving the image from DockerHub to CERN's image registry

There are no artifacts in the registry.cern.ch/cmsweb/rucio-tracers, but it could be that we need to add -stable to the end of the tags so it remains in the registry.