如何用Jenkins的HTTP_PROXY后面的Dockerfile构建Docker镜像？

构建Docker镜像在桌面上工作没有问题.安装Node.js NPM依赖项正常工作.但是,当使用在公司代理后面托管的持续集成服务器(如Jenkins)时,构建Docker Images会失败.

Node.js NPM依赖项

在构建Node.js pacakges时,命令npm install在克隆GIT依赖项时无法连接到GIT时失败.

e1ce5e8407d1: Already exists
Status: Image is up to date for node:0.10.33
 ---> e1ce5e8407d1
Step 1 : RUN mkdir -p /usr/src/app
 ---> Using cache
 ---> 965cad0c68b0
Step 2 : WORKDIR /usr/src/app
 ---> Using cache
 ---> 4c498f0c07e9
Step 3 : COPY package.json /usr/src/app/
 ---> b0662a8275fb
Removing intermediate container 5aca20551452
Step 4 : RUN npm install
 ---> Running in 7ccf9e5362af
npm WARN package.json newww@2.0.0 No README data
npm WARN package.json Dependency 'async-cache' exists in both dependencies and devDependencies, using 'async-cache@^0.1.5' from dependencies
npm ERR! git clone https://github.com/npm/npm2es.git Cloning into bare repository '/root/.npm/_git-remotes/https-github-com-npm-npm2es-git-60a75edb'...
npm ERR! git clone https://github.com/npm/npm2es.git fatal: unable to access 'https://github.com/npm/npm2es.git/': Failed to connect to github.com port 443: Connection timed out

Java Maven,Ruby,Go Docker Image with Dependencies

构建Java,Ruby或Go容器时也会出现同样的情况,其中依赖项位于公司代理服务器上的存储库服务器中.

知道您可以使用HTTP_PROXY环境变量配置Docker,如何正确配置Docker以在CI环境中正确构建映像？

注意:Docker 1.9 可能有助于解决此问题:

" 问题14634 ":构建器 - 构建时参数传递(例如HTTP_PROXY)

" PR 15182 ":支持在构建上下文中传递构建时变量

用法(建议):

docker build --build-arg http_proxy=http://my.proxy.url  --build-arg foo=bar <
ARG --description="foo's description" foo
USER $foo
MARK

Docker守护程序HTTP代理

有很多关于为Docker的守护进程设置HTTP_PROXY环境变量的文档.环境变量仅在运行容器时可用,因此在这里对我们没有帮助.

Dockerfile中的解决方案

虽然在Dockerfile中设置环境变量HTTP_ENV或http_env可能会有所帮助,但它也无济于事.

ENV http_proxy http://proxy.mycompany.com:80

原因是每个特定服务仅以不同方式遵循HTTP代理设置.我可以解决的方法如下.

NPM:NPM需要使用CLI命令设置HTTP_PROXY变量.

GIT:GIT也需要使用CLI命令设置HTTP_PROXY变量.

MAVEN:MVN命令要求将HTTP_PROXY设置为〜/ .m2/settings.xml用户目录下的XML文件.对于Docker,您可以将其添加到根目录的"/root/.m2/settings.xml"目录(不安全,仅限开发)或Dockerfile的用户主目录.

例如,使用Dockerfile运行应用程序,我可以使用以下Dockerfile构建映像:

FROM node:0.10.33

# Prepare
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app

# Use the cache for dependencies
COPY package.json /usr/src/app/

# If building behind an http_proxy, set them for git and npm
RUN git config --global http.proxy http://qypprdproxy02.ie.company.net:80 && \
    npm config set proxy http://qypprdproxy02.ie.company.net:80 && \
    npm config set https-proxy http://qypprdproxy02.ie.company.net:80

# Install dependencies
RUN npm install

# Copy all the source
COPY . /usr/src/app

# Execute the dev steps
COPY ./numbat-config.example.js /usr/src/app/numbat-config.js
COPY ./.env.example /usr/src/app/.evn
RUN touch /usr/src/app/config.admin.js

请注意,我已使用CLI命令配置了GIT和NPM,以便在运行NPM安装命令之前显式获取代理设置.这样,NPM和GIT依赖关系将分别自动检索和克隆.

使用此Dockerfile构建映像的结果按预期工作:

[root@pppdc9prd6dq newww]# fig build
...
...
Building npmregistryserver...
 ---> Using cache
 ---> 965cad0c68b0
Step 2 : WORKDIR /usr/src/app
 ---> Using cache
 ---> 4c498f0c07e9
Step 3 : COPY package.json /usr/src/app/
 ---> ae8ff7861246
Removing intermediate container ba1d7b8c9963
Step 4 : RUN npm config set proxy http://qypprdproxy02.ie.company.net:80 &&     npm config set https-proxy http://qypprdproxy02.ie.company.net:80 &&     npm install
 ---> Running in aa6e05d9c7a4
npm WARN package.json newww@2.0.0 No README data
npm WARN package.json Dependency 'async-cache' exists in both dependencies and devDependencies, using 'async-cache@^0.1.5' from dependencies
npm WARN deprecated extend@1.1.3: Please update to the latest version.

> v8flags@1.0.8 install /usr/src/app/node_modules/gulp/node_modules/v8flags
> node fetch.js


> hiredis@0.1.17 install /usr/src/app/node_modules/hiredis
> node-gyp rebuild

make: Entering directory '/usr/src/app/node_modules/hiredis/build'
  CC(target) Release/obj.target/hiredis/deps/hiredis/hiredis.o
  CC(target) Release/obj.target/hiredis/deps/hiredis/net.o
  CC(target) Release/obj.target/hiredis/deps/hiredis/sds.o
  CC(target) Release/obj.target/hiredis/deps/hiredis/async.o
  AR(target) Release/obj.target/deps/hiredis.a
  COPY Release/hiredis.a
  CXX(target) Release/obj.target/hiredis/src/hiredis.o
  CXX(target) Release/obj.target/hiredis/src/reader.o
  SOLINK_MODULE(target) Release/obj.target/hiredis.node
  SOLINK_MODULE(target) Release/obj.target/hiredis.node: Finished
  COPY Release/hiredis.node
make: Leaving directory '/usr/src/app/node_modules/hiredis/build'
npm WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"0.10.33","npm":"2.1.11"})

> pngcrush-bin@1.0.0 postinstall /usr/src/app/node_modules/imagemin-pngcrush/node_modules/pngcrush-bin
> node lib/install.js

     fetch : https://raw.githubusercontent.com/imagemin/pngcrush-bin/v1.0.0/vendor/linux/pngcrush


? pre-build test passed successfully!

> dtrace-provider@0.3.1 install /usr/src/app/node_modules/npm-typeahead/node_modules/restify/node_modules/dtrace-provider
> scripts/install.js

npm WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"0.10.33","npm":"2.1.11"})
npm WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"0.10.33","npm":"2.1.11"})
npm WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"0.10.33","npm":"2.1.11"})
npm WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"0.10.33","npm":"2.1.11"})
npm WARN cannot run in wd newww@2.0.0 gulp build (wd=/usr/src/app)
newww-metrics@1.0.0 node_modules/newww-metrics

murmurhash@0.0.2 node_modules/murmurhash

npm-humans@2.0.1 node_modules/npm-humans

leven@1.0.1 node_modules/leven

chunk@0.0.2 node_modules/chunk

npm-expansions@1.14.0 node_modules/npm-expansions

similarity@1.0.1 node_modules/similarity

truncate@1.0.4 node_modules/truncate

这正常按预期工作,您可以在http代理后面有一个CI/CD环境,以根据此Dockerfile重建图像.

我必须做

docker build --no-cache --build-arg HTTP_PROXY=$http_proxy \
--build-arg HTTPS_PROXY=$http_proxy --build-arg NO_PROXY="$no_proxy" \
--build-arg http_proxy=$http_proxy --build-arg https_proxy=$http_proxy \
--build-arg no_proxy="$no_proxy" -t myContainer /path/to/Dockerfile/directory

在我的bashrc中设置的位置$http_proxy和位置$no_proxy。我使用了两者HTTP_PROXY，http_proxy因为不同的实用程序将检查不同的变量（同时curl检查两个变量，wget仅检查小写的变量，等等）。设置ENV http_proxy http://proxy.mycompany.com:80没有帮助，因为我试图在构建时而不是运行时使用这些变量。