Re: Enviroment variables HTTP_PROXY for CF CLI doen't work


JT Archie <jarchie@...>
 

Yu,

The environment variable HTTP_PROXY needs to be attached to the app, not
just the box.

On your app set the environment variable with `cf set-env <app_name>
HTTP_PROXY <proxy_server>`.

Then try to `cf push`.

Kind Regards,

JT

On Wed, Jan 27, 2016 at 4:40 AM, Yu, Yongcong <yuyc(a)cn.fujitsu.com> wrote:

Hello CF-dev community members!

I deployed CF on a PC with cf_nise_installer.
When pushing a app with a online buildpack as following, it's failed.
########################################################
cf push -b https://github.com/cloudfoundry/java-buildpack
Using manifest file /home/yuyc/svn/SampleAPP/Java/manifest.yml

Creating app business in org DevBox / space sp1 as admin...
OK

Creating route business.10.167.227.48.xip.io...
OK

Binding business.10.167.227.48.xip.io to business...
OK

Uploading business...
Done uploading
OK

Starting app business in org DevBox / space sp1 as admin...
-----> Downloaded app package (36K)
Cloning into '/tmp/buildpacks/java-buildpack'...
fatal: unable to access 'https://github.com/cloudfoundry/java-buildpack/':
Failed to connect to 10.167.227.38 port 1080: Connection refused
Cloning into '/tmp/buildpacks/java-buildpack'...
fatal: unable to access 'https://github.com/cloudfoundry/java-buildpack/':
Failed to connect to 10.167.227.38 port 1080: Connection refused
/var/vcap/packages/dea_next/buildpacks/lib/git.rb:23:in `clone': Git clone
failed: git clone --recursive
https://github.com/cloudfoundry/java-buildpack
/tmp/buildpacks/java-buildpack (RuntimeError)
from
/var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:154:in
`clone_buildpack'
from
/var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:120:in `build_pack'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:83:in
`block in compile_with_timeout'
from /usr/lib/ruby/1.9.1/timeout.rb:69:in `timeout'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:82:in
`compile_with_timeout'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:58:in
`block in stage_application'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:53:in
`chdir'
from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:53:in
`stage_application'
from /var/vcap/packages/dea_next/buildpacks/bin/run:10:in `<main>'


FAILED
StagingError
########################################################

Git clone has also been successfully worked on the host of CF where setup
the same environment variables HTTP_PROXY.
So, it looks like that HTTP_PROXY doesn't work when pushing app.

The problem happens at the time of starting app, so it seems that the
warden container can't access to the internet via HTTP_PROXY.
I also login the warden container and get the route of it, but I can't
ping the gateway on it.
The gateway of the warden container is assigned by the warden server, but
I found the gateway doesn't have a IP of IPV4
Cloud you tell me how to fix this problem?

Best wishes for you.
------------------------------------------------------------
Yu Yongcong
Development Dept. I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
No.6 Wenzhu Road, Software Avenue, Nanjing, 210012, China
TEL: +86+25-86630566-8626
COINS: 7998-8626
FAX: +86+25-83317685
http://www.fujitsu.com/cn/fnst/ MAIL: yuyc(a)cn.fujitsu.com
------------------------------------------------------------




Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.