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

Cannot override /tmp volume mount

    Details

    • Similar Issues:

      Description

      We run our regression tests in docker to make sure they not interfere however
      plugins seems to force mounting /tmp:/tmp which is shared between containers,
      which means tests will interfere with each other. I want to mount /tmp/${BUILD_NUMBER}:/tmp. However if I specify that build is failing because /tmp passed again with a different value (besides being passed twice and var not expanding which is different bug)
      14:14:31 Error response from daemon: Duplicate bind mount /tmp
      14:14:31 FATAL: Failed to run docker image

      docker run --tty --detach --privileged --workdir /var/lib/jenkins/jobs/build-gerrit-master/workspace --volume /tmp/${BUILD_NUMBER}:/tmp:rw --volume /tmp/467:/tmp:rw --volume /var/lib/jenkins:/var/lib/jenkins:rw --volume /tmp:/tmp:rw

      So it either should not pass /tmp mount point if it see that user defined one, or it should allow to complete override everything that plugin want to pass by default.

        Attachments

          Activity

          Hide
          mryan Manuel Ryan added a comment -

          Mounting /tmp is required for executing shell build steps, the shell script is written in /tmp by the master/slave and read from the build container, if you don't share it directly, you'll have a FileNotFound.

          Show
          mryan Manuel Ryan added a comment - Mounting /tmp is required for executing shell build steps, the shell script is written in /tmp by the master/slave and read from the build container, if you don't share it directly, you'll have a FileNotFound.
          Hide
          dantran dan tran added a comment -

          besides shell script executions, is there anything else we should be aware of.

          we also run into random temp file collision during heavy multi-active container builds in parallel

          Show
          dantran dan tran added a comment - besides shell script executions, is there anything else we should be aware of. we also run into random temp file collision during heavy multi-active container builds in parallel

            People

            • Assignee:
              Unassigned
              Reporter:
              elaskavaia Elena Laskavaia
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: