-
Notifications
You must be signed in to change notification settings - Fork 23
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
HTTP_PROXY, NO_PROXY settings #17
Comments
I think I am affecting by this: aws/aws-sdk-go#1226 |
Yeah the container doesn't seem to have a roll attached, but |
Sorry for the late reply. I'll have a look at the above issue. |
yep I setup http_proxy https_proxy and no_proxy. To be honest I get the same error running I have also applied the same role on my instance as my task. :/ |
@codesuki Actually, just thinking over the weekend, I think my issue is: aws/amazon-ecs-agent#605. I'm not able to test right now, but will check it on Monday. I have the |
Let me know the results! |
Cool yep that was my issue. I also had to add my own host to the result, err := sendHTTRequest("http://" + host + ":51678/v1/metadata") which means I have to dynamically modify the |
The call we cannot avoid, I think, but I will replace that by localhost. |
Hmm, I'm not too keen on adding But I see this is possible: so thats probably my best bet yeah? |
At the moment yes. Although I can't promise it I'll try to change it to localhost today and make a release. |
I don't see how setting the API call to hit localhost will work if it has to hit the host machine (assuming you are using a bridged network)? |
Hahaha, good point! That's why I had to get the IP of the machine in the first place. |
Closing issue, since issue has been resolved! |
I'm getting the following running ecs-gen on a container.
The text was updated successfully, but these errors were encountered: