Hello Roman, Thanks for the advice. I tried exporting proxy environment variables as per your advice, However my airship-in-a-bottle installation ended on same error as mentioned before. Am I missing something?Does airship-in-a-bottle installation works behind the proxy? Any help would be appreciated. Best regards, Fumiya Suga -----Original Message----- From: Roman Gorshunov <paye600@gmail.com> Sent: Tuesday, January 22, 2019 5:25 PM To: airship-discuss@lists.airshipit.org Subject: Re: [Airship-discuss] dev_single_node behind proxy Hello Fumiya, You probably forgot to export environment variables https://airship-treasuremap.readthedocs.io/en/latest/airskiff.html#proxy-con... . If it would not help, let me know, and I will run full test with a proxy and will try for resolve the issue. Thank you for trying Airship! Best regards, -- Roman Gorshunov On Tue, Jan 22, 2019 at 7:41 AM 須賀文哉 <fumiya.suga@as.ntt-at.co.jp> wrote:
Hi all, I am a newbie to Airship. I tried installing the dev_single_node behind corporate proxy. I configured the environment file as mentioned in proxy setting for dev_minimal,which didn't go well. Following is the snippet of the error.
***snip**** + wait_for_kubernetes_api 3600 + set +x Tue Jan 15 15:35:02 JST 2019 Waiting 3600 seconds for API response. Unable to find image 'gcr.io/google_containers/hyperkube-amd64:v1.10.2' locally docker: Error response from daemon: Get https://gcr.io/v2/: dial tcp 108.177.97.82:443: connect: no route to host. See 'docker run --help'. *******
I would be thankful if you could answer me configuration for deploying dev_single_node behind proxy.
Any help would be appreciated.
Best regards, Fumiya Suga
_______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
_______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss