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

Bug Build step fail when try connect to another container/image

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • docker-slaves-plugin

      I'm starting to change from VM to Docker slaves on my Jenkins installation but something is wrong.

      I've watched the videos published here http://blog.loof.fr/2015/09/introducing-docker-slaves-jenkins-plugin.html, but always jump an error.

      I think that problem are the tools versions that I'm using.

      Can be possible know what are the minimum version of Jenkins, Docker and Java for successful run a job?

      Actually, I can't see Docker containers logs because "logs" command is supported only for "json-file" and "journald" logging drivers.

        1. jenkins-job.log
          1 kB
        2. jenkins.log
          4 kB
        3. docker.log
          2 kB

          [JENKINS-42818] Bug Build step fail when try connect to another container/image

          Yunier Sosa created issue -
          Yunier Sosa made changes -
          Environment Original: Debian 9
          Jenkins 2.33.3 Stable version
          Docker CE 17.03, API Version 1.26
          Docker Slaves Plugin 1.0.6
          openjdk version "1.8.0_121"
          OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-4-b13)
          OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
          		 New: Debian 9
          Jenkins 2.32.3 Stable version
          Docker CE 17.03, API Version 1.26
          Docker Slaves Plugin 1.0.6
          openjdk version "1.8.0_121"
          OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-4-b13)
          OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)

          Yunier Sosa added a comment -

          After various test, I see that during build execution:

          • I can see the WS and all files while cloning from GitHub.
          • The build finished SUCCESS (only clone step)
          • I can't execute more steps because the WS is missing and this error is triggered:
            Error response from daemon: Container 8a5e082967db812c09218cd088786343a0382f2bc3e2c61d7b7b7539223d8e6a is not running
            Build step 'Execute shell' marked build as failure

          With data provided by Docker Build Context link of each build I navigate to my local /var/lib/docker/volumes/17df2ffd9f2b0765ecb5b277db9aba4aaee60cf1d839da2fca562682426ed01c/_data/workspace/Docker_Test and Yahoo!,  here are the files.

          But Jenkins can't locate those files, needed for next steps.

          Any idea?

          Yunier Sosa added a comment - After various test, I see that during build execution: I can see the WS and all files while cloning from GitHub. The build finished SUCCESS (only clone step) I can't execute more steps because the WS is missing and this error is triggered: Error response from daemon: Container 8a5e082967db812c09218cd088786343a0382f2bc3e2c61d7b7b7539223d8e6a is not running Build step 'Execute shell' marked build as failure With data provided by Docker Build Context link of each build I navigate to my local /var/lib/docker/volumes/17df2ffd9f2b0765ecb5b277db9aba4aaee60cf1d839da2fca562682426ed01c/_data/workspace/Docker_Test and Yahoo!,  here are the files. But Jenkins can't locate those files, needed for next steps. Any idea?

          Nicolas De Loof added a comment -

          Issue tracker is not a forum, please join jenkins-users to request assistance

          Nicolas De Loof added a comment - Issue tracker is not a forum, please join jenkins-users to request assistance
          Nicolas De Loof made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            ndeloof Nicolas De Loof
            yjsosa Yunier Sosa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: