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

docker.inside to rely on runC

    XMLWordPrintable

Details

    Description

      docker.inside does a bind mount of the workspace, assuming the docker daemon is a local one. If we admit this assumption, then we should better rely on runC (docker 1.11 and later) that allows to exec inside a container with support for --env and --cwd, two options that `docker exec` doesn't support (and won't support, according to docker roadmap)

      This would allow to avoid relying on `env` hack (https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L225) and fix JENKINS-33510

      Attachments

        Issue Links

          Activity

            jglick Jesse Glick added a comment -

            assuming the docker daemon is a local one

            Need not be, but it must be able to share the workspace as a filesystem, which also works if the agent is inside a container on the same daemon port.

            Do you have any concrete proposal here?

            jglick Jesse Glick added a comment - assuming the docker daemon is a local one Need not be, but it must be able to share the workspace as a filesystem, which also works if the agent is inside a container on the same daemon port. Do you have any concrete proposal here?

            People

              Unassigned Unassigned
              ndeloof Nicolas De Loof
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: