Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
RedOnePrime opened this issue Mar 4, 2019 · 2 comments
Open

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

RedOnePrime opened this issue Mar 4, 2019 · 2 comments

Comments

@RedOnePrime
Copy link

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
Copy link
Member

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
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants