Google Cloud SDK 0.9.39 still fails to do setup-managed-vms -


i updated gcloud components on os x mavericks laptop, have:

$ gcloud version google cloud sdk 0.9.39  $ boot2docker version boot2docker-cli version: v1.3.2 git commit: e41a9ae 

i hoping managed vms setup work, alas:

$ gcloud preview app setup-managed-vms select runtime download base image for:  [1] go  [2] java  [3] python27  [4] please enter numeric choice (4):  2  pulling base images runtimes [java] google cloud storage pulling image: google/appengine-java traceback (most recent call last):   file "/users/hussein/google-cloud-sdk/./lib/googlecloudsdk/gcloud/gcloud.py", line 175, in <module>     main()   file "/users/hussein/google-cloud-sdk/./lib/googlecloudsdk/gcloud/gcloud.py", line 171, in main     _cli.execute()   file "/users/hussein/google-cloud-sdk/./lib/googlecloudsdk/calliope/cli.py", line 385, in execute     post_run_hooks=self.__post_run_hooks, kwargs=kwargs)   file "/users/hussein/google-cloud-sdk/./lib/googlecloudsdk/calliope/frontend.py", line 274, in _execute     pre_run_hooks=pre_run_hooks, post_run_hooks=post_run_hooks)   file "/users/hussein/google-cloud-sdk/./lib/googlecloudsdk/calliope/backend.py", line 928, in run     result = command_instance.run(args)   file "/users/hussein/google-cloud-sdk/lib/googlecloudsdk/appengine/app_commands/setup_managed_vms.py", line 39, in run     args.image_version)   file "/users/hussein/google-cloud-sdk/./lib/googlecloudsdk/appengine/lib/images/pull.py", line 54, in pullbasedockerimages     util.pullspecifiedimages(docker_client, image_names, version, bucket)   file "/users/hussein/google-cloud-sdk/./lib/googlecloudsdk/appengine/lib/images/util.py", line 232, in pullspecifiedimages     'error pulling {image}: {e}'.format(image=image_name, e=e)) googlecloudsdk.appengine.lib.images.util.dockerpullerror: error pulling google/appengine-java: 500 server error: internal server error ("invalid registry endpoint "http://localhost:49153/v1/". https attempt: https://localhost:49153/v1/_ping: read tcp 127.0.0.1:49153: connection reset peer. http attempt: http://localhost:49153/v1/_ping: read tcp 127.0.0.1:49153: connection reset peer") 

i'm new docker , managed vas, , i'm wondering if issue due boot2docker port forwarding setup. env setup correctly think;

$ env | grep docker docker_host=tcp://192.168.59.103:2376 docker_tls_verify=1 docker_cert_path=/users/h/.boot2docker/certs/boot2docker-vm 

with docker host ip being:

$ boot2docker ip docker@localhost's password:   vm's host interface ip address is: 192.168.59.103 

finally, containers on system far are:

$ docker ps -a container id        image                             command             created               status                           ports                    names 73c6d317a631        google/docker-registry:latest     "./run.sh"          2 minutes ago           exited (-1) minute ago                            goofy_archimedes                    40b709d6fa00        gcloud-credentials-image:latest   "/true"             2 minutes ago       exited (0) 2 minutes ago                                  gcloud-credentials-1417828737.2     a3073bc56ff2        google/docker-registry:latest     "./run.sh"          47 hours ago        exited (-1) 47 hours ago                                  distracted_bell                     1b6fe130af45        11cd171d89b3                      "/true"             47 hours ago        exited (0) 47 hours ago                                   gcloud-credentials-1417707423.48    28c181e66b11        google/docker-registry:latest     "./run.sh"          2 days ago          exited (0) 4 minutes ago         0.0.0.0:5000->5000/tcp   elegant_darwin                      

then why gcloud python script trying access registry on localhost? someone, please show me light!


Comments

Popular posts from this blog

python - mat is not a numerical tuple : openCV error -

c# - MSAA finds controls UI Automation doesn't -

wordpress - .htaccess: RewriteRule: bad flag delimiters -