It is impossible to run a container pulled from a registry if a local build is available

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            Matthew Walker
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: