Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29775

client is too old, minimum supported API version is 1.12

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Not A Defect
    • Labels:
    • Environment:
      Jenkins: 1.609.2
      docker-build-step: 1.28
      docker-commons: 1.2
      docker remote server: 1.7.1
      OS: Ubuntu 14.04
      JDK: 1.8.0-45
    • Similar Issues:

      Description

      Trying to build an image, I'm getting this exception:
      com.github.dockerjava.api.BadRequestException: client is too old, minimum supported API version is 1.12, please upgrade your client to a newer version

      Docker v1.7 is not supported?

        Attachments

          Activity

          Hide
          cfurmaniak cfurmaniak added a comment -

          check that you entered the API version and not the docker version in the "version" input

          Show
          cfurmaniak cfurmaniak added a comment - check that you entered the API version and not the docker version in the "version" input
          Hide
          milansimonovic Milan Simonovic added a comment -

          sorry, what do you mean by this?

          Show
          milansimonovic Milan Simonovic added a comment - sorry, what do you mean by this?
          Hide
          zxkane Meng Xin Zhu added a comment -

          He meat you have to specify the docker client API version in docker step plugin of Jenkins global configuration.

          It works fine for me after corrected the version of client API in global configuration.

          Show
          zxkane Meng Xin Zhu added a comment - He meat you have to specify the docker client API version in docker step plugin of Jenkins global configuration. It works fine for me after corrected the version of client API in global configuration.
          Hide
          vjuranek vjuranek added a comment -

          Milan Simonovic, yes, setting up client version in global Jenkins configuration should solve the issue. Could you confirm it works for you?

          Show
          vjuranek vjuranek added a comment - Milan Simonovic , yes, setting up client version in global Jenkins configuration should solve the issue. Could you confirm it works for you?
          Hide
          milansimonovic Milan Simonovic added a comment -

          sorry, but i had to quickly find a workaround so i'm not using this plugin, can't really confirm, but feel free to close the issue if it works for you and doesn't when you remove the config.

          Show
          milansimonovic Milan Simonovic added a comment - sorry, but i had to quickly find a workaround so i'm not using this plugin, can't really confirm, but feel free to close the issue if it works for you and doesn't when you remove the config.
          Hide
          vjuranek vjuranek added a comment -

          thanks for info, closing then

          Show
          vjuranek vjuranek added a comment - thanks for info, closing then

            People

            • Assignee:
              vjuranek vjuranek
              Reporter:
              milansimonovic Milan Simonovic
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: