[JENKINS-52866] It is impossible to run a container pulled from a registry if a local build is available

Due to the change made for JENKINS-34276, if a local build of a container exists then the version from the specified registry will never be run.

This causes us problems as we have several jenkins slaves, each of which can run a job which builds a container and other jobs which use that container. docker.image().inside always runs the most recent (potentially outdated) local build instead of the one from the registry.

If reverting the change from JENKINS-34276 is unacceptable then we would need a way to force the use of the version from the registry.

---
Originally reported by matthewwalker, imported from: It is impossible to run a container pulled from a registry if a local build is available

• status: Open
  
• priority: Major
  
• component(s): docker-workflow-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-07
  

Raw content of original issue

Due to the change made for JENKINS-34276, if a local build of a container exists then the version from the specified registry will never be run.


This causes us problems as we have several jenkins slaves, each of which can run a job which builds a container and other jobs which use that container. docker.image().inside always runs the most recent (potentially outdated) local build instead of the one from the registry.


If reverting the change from JENKINS-34276 is unacceptable then we would need a way to force the use of the version from the registry.