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

Running a project outside docker after specifying a dockerfile results in jenkins trying to run docker on the non-docker host

XMLWordPrintable

      I set up an example repository to demonstrate the problem: https://github.com/derphilipp/jenkins_docker_host_bug

       

      We assume we have a node/slave/agent to run docker on (label "docker")
      and a non-docker node/slave/agent (here: raspberrypi).

       

      Although the second step in the file has a different agent set, Jenkins still tries to call the docker command to set up something which results in file-not-found exception in Java (see README.md of the example project)

       

      In this example it could be fixed by specifying the node/agent/slave not for the whole pipeline but for the first step, but I want the use the default for every step in a longer Jenkinsfile.

          [JENKINS-50897] Running a project outside docker after specifying a dockerfile results in jenkins trying to run docker on the non-docker host

          Philipp Weißmann created issue -
          Philipp Weißmann made changes -
          Description Original: I set up an example repository to demonstrate the problem: [https://github.com/derphilipp/jenkins_docker_host_bug]

           

          We assume we have a node/slave/agent to run docker on (label "docker")
          and a non-docker node/slave/agent (here: raspberrypi).

           

          Although the second step in the file has a different agent set, Jenkins still tries to call the docker command to set up something which results in file-not-found exception in Java (see README.md of the example project)           		New: I set up an example repository to demonstrate the problem: [https://github.com/derphilipp/jenkins_docker_host_bug]

           

          We assume we have a node/slave/agent to run docker on (label "docker")
           and a non-docker node/slave/agent (here: raspberrypi).

           

          Although the second step in the file has a different agent set, Jenkins still tries to call the docker command to set up something which results in file-not-found exception in Java (see README.md of the example project)

           

          In this example it could be fixed by specifying the node/agent/slave not for the whole pipeline but for the first step, but I want the use the default for every step in a longer Jenkinsfile.
          Nicolas De Loof made changes -
          Component/s New: docker-workflow-plugin [ 20625 ]
          Component/s Original: core [ 15593 ]
          Component/s Original: docker [ 20834 ]
          Component/s Original: pipeline [ 21692 ]
          Nicolas De Loof made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]
          Nicolas De Loof made changes -
          Component/s New: pipeline-model-definition-plugin [ 21706 ]
          Component/s Original: docker-workflow-plugin [ 20625 ]
          Andrew Bayer made changes -
          Link New: This issue duplicates JENKINS-46831 [ JENKINS-46831 ]
          Andrew Bayer made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Liam Newman made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            derphilipp Philipp Weißmann
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: