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

Using a docker agent from a private registry does pass the proxy configuration to the docker container

    Details

    • Similar Issues:
    • Released As:
      Docker Commons Plugin 1.15

      Description

      I assume that this is not an issue with the model definition itself, but elsewhere. However I just experienced it when configuring a docker agent that uses an image from a private registry. In this case the corporate proxy settings (which are configured in .docker/config.json) and which are usually passed by the docker daemon to the container (via the HTTP(S)_PROXY/NO_PROXY environment variables) are missing from the container. If I switch to a DockerHub image (e.g. ubuntu:16.04), the proxy settings are present in the container.

      This is more or less the same issue as JENKINS-52724, but manifested when using a docker agent and not when building a docker image.

        Attachments

          Activity

          Hide
          bitwiseman Liam Newman added a comment -

          Bulk closing resolved issues.

          Show
          bitwiseman Liam Newman added a comment - Bulk closing resolved issues.

            People

            • Assignee:
              Unassigned
              Reporter:
              kvalev Krassimir Valev
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: