谷歌應用程序引擎部署自定義虛擬機的應用程序需要很長的時間來部署

Question

這裏是我的worker.yaml

runtime: custom #python27 
api_version: 1 
threadsafe: false 
vm: true 
service: worker 
env_variables: 
    PYTHON_ENV: lab 
network: 
    instance_tag: testing123 
    name: dev 


handlers: 
- url: /.* 
    script: Framework.Workers.PushQueues.worker.app 
    login: admin 

Dockerfile

FROM us.gcr.io/smiling-diode-638/basic-algo-docker-v2 

和控制檯輸出：

gcloud app deploy worker.yaml --verbosity='debug'        ✱ 
DEBUG: Running gcloud.app.deploy with Namespace(__calliope_internal_deepest_parser=ArgumentParser(prog='gcloud.app.deploy', usage=None, description='Deploy the local code and/or configuration of your app to App Engine.', version=None, formatter_class=<class 'argparse.HelpFormatter'>, conflict_handler='error', add_help=False), account=None, authority_selector=None, authorization_token_file=None, bucket=None, calliope_command=<googlecloudsdk.calliope.backend.Command object at 0x108770290>, command_path=['gcloud', 'app', 'deploy'], configuration=None, credential_file_override=None, deployables=['worker.yaml'], docker_build=None, document=None, flatten=None, format=None, h=None, help=None, http_timeout=None, ignore_bad_certs=False, image_url=None, log_http=None, project=None, promote=None, quiet=None, server=None, skip_image_url_validation=False, skip_staging=False, stop_previous_version=None, trace_email=None, trace_log=None, trace_token=None, user_output_enabled=None, verbosity='debug', version=None). 
DEBUG: API endpoint: [https://appengine.googleapis.com/], API version: [v1beta5] 
You are about to deploy the following services: 
- smiling-diode-638/worker/20161109t165841 (from [/Volumes/ownhealth_dev/Backend/worker.yaml]) 
    Deploying to URL: [https://worker-dot-smiling-diode-638.appspot.com] 

Do you want to continue (Y/n)? Y 

DEBUG: No bucket specified, retrieving default bucket. 
DEBUG: Using bucket [gs://staging.smiling-diode-638.appspot.com/]. 
If this is your first deployment, this may take a while...DEBUG: Host: appengine.google.com 
DEBUG: _Authenticate configuring auth; needs_auth=False 
DEBUG: Sending request to https://appengine.google.com/api/vms/prepare?app_id=smiling-diode-638 headers={'X-appcfg-api-version': '1', 'content-length': '0', 'Content-Type': 'application/octet-stream'} body= 
INFO: Attempting refresh to obtain initial access_token 
INFO: Refreshing access_token 
If this is your first deployment, this may take a while...\DEBUG: Got response: {bucket: vm-containers.smiling-diode-638.appspot.com, path: /containers} 

If this is your first deployment, this may take a while...done. 

Beginning deployment of service [worker]... 
DEBUG: No staging command found for runtime [custom] and environment [MANAGED_VMS]. 
WARNING: Deployment of App Engine Flexible Environment apps is currently in Beta 
INFO: Using Dockerfile found in /Volumes/ownhealth_dev/Backend 
Building and pushing image for service [worker] 


INFO: Refreshing access_token 
INFO: Uploading [/var/folders/d1/lgf326px48s8w6cvj2f7ng200000gp/T/tmplQDUjR/src.tgz] to [us.gcr.io/smiling-diode-638/appengine/worker.20161109t165841:latest] 

圖像爲3.5GB

已經有一個多小時了，它仍在部署。

編輯： 我試圖從本地網絡設備部署和它確實更快地下載圖像，但是部署是無止境的，我越來越Error Response: [4] DEADLINE_EXCEEDED

所有我在掛接看到錯誤 ERROR: build step "gcr.io/cloud-builders/docker@sha256:1b5a8642d04ef785f7dd2dbb0296f837895f50442fdfe5ebd0b04c206ab0b1b5" failed: exit status 2 我可以在哪裏檢查日誌？

編輯＃2：

我跑像這樣

gcloud preview app deploy worker.yaml --image-url=us.gcr.io/smiling-diode-638/basic-algo-docker-v2 --verbosity='debug' 

越來越 Error Response: [13] Timed out when starting VMs. It's possible that the application code is unhealthy

但我已將此添加到worker.yaml

health_check: 
    enable_health_check: False 

所以怎麼辦我禁用健康檢查？

Answer 1

很大一部分部署時間經常用於上傳Docker鏡像，很大程度上取決於鏡像大小（您的情況相當大 - 3.5GB），您的Internet連接上傳速度和服務器與GAE的「貼近度」地區數據中心。

你可能會從一個雲託管的虛擬機（理想的是GCE在同一區域託管作爲您的GAE應用程序的機器）執行部署得到顯著的上傳速度提升。

建設中的形象還需要時間，它的一些不可避免的。你也許可以加快步伐了一下，見How can I speed up Rails Docker deployments on Google Cloud Platform?

此外，重新部署的應用程序相比，第一個應用程序部署需要一些不可避免的額外步驟時，看到why does google appengine deployment take several minutes to update service