winfs-inject doesn't work on windows behind a proxy

RedOnePrime commented 5 years ago

We have a jumpbox in the environment behind a proxy and winfs-injector throws the following error.

winfs-injector-windows.exe --input-tile pas-windows-2.3.7-build.16.pivotal --output-tile pas-windows-2.3.7-build.16-INJECTED.pivotal

Get https://auth.docker.io/token?service=registry.docker.io&scope=repository:cloudfoundry/windows2016fs:pull: dial tcp 34.206.236.31:443: i/o timeout

I have tried setting netsh and also http/s_proxy environment variables since it is written in go thinking that might work, but nada. The instructions located https://docs.pivotal.io/pivotalcf/2-3/windows/installing.html#install do not specify requiring direct internet acces so I was assuming I could configure the proxy somehow.

If I can provide any more details let me know

cf-gitbot commented 5 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

genevieve commented 5 years ago

Hey @RedOnePrime. How were you setting the http/s_proxy environment variable on your windows vm? You are correct - we are using the default golang http client and it automatically picks up those environment variables.

pivotal-cf / winfs-injector

winfs-inject doesn't work on windows behind a proxy #7