Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin

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

XMLWordPrintable

      The `--force` flag is still being set to true for Pipeline Docker build and publish steps. I'm running into the issue when executing a job to build and publish an image to a registry:
      + docker tag --force=true foo:tag foo:tag
      unknown flag: --force
      See 'docker tag --help'.
      The relevant bit from my Jenkinsfile:
      node {
      stage('deploy')

      { git branch: 'feature/branch', credentialsId: 'foo-key', url: 'git@github.com:bar/baz.git' withDockerRegistry([credentialsId: 'ecr:us-east-1:foo-key', url: 'https://etcetera/']) { docker.image('foo:tag').push() }

            Assignee:
            Unassigned
            Reporter:
            Jack Brooks
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: