【问题标题】:google app engine deploy a custom vm app takes a long time to deploy谷歌应用引擎部署自定义 vm 应用需要很长时间才能部署
【发布时间】:2017-03-23 11:42:25
【问题描述】:

这是我的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

那么我该如何禁用健康检查呢??

【问题讨论】:

    标签: google-app-engine containers google-cloud-platform google-kubernetes-engine


    【解决方案1】:

    部署时间的很大一部分通常用于上传 docker 映像,这在很大程度上取决于映像大小(在您的情况下相当大 - 3.5GB)、您的互联网连接上传速度以及您的服务器与 GAE 区域的“接近度”数据中心。

    通过从云托管的 VM(最好是与 GAE 应用托管在同一区域的 GCE 机器)执行部署,您可能会显着提高上传速度。

    构建映像也需要时间,其中一些是不可避免的。您也许可以加快一点速度,请参阅How can I speed up Rails Docker deployments on Google Cloud Platform?

    此外,与第一次部署应用相比,重新部署应用时需要一些不可避免的额外步骤,请参阅why does google appengine deployment take several minutes to update service

    【讨论】:

    • Dan,我收到了Error Response: [13] Timed out when starting VMs. It's possible that the application code is unhealthy,即使我禁用了健康检查。如何跳过健康检查?
    • 不确定(我实际上还没有使用灵活的环境)。文档对于是否强制进行健康检查有点矛盾。我会尝试使用 --no-promote--no-stop-previous-version 部署选项来缩小部署范围,可能是指定版本 - 试图不让部署回滚。如果我得到一个虚拟机,那么在尝试将其作为 GAE 应用程序进行调试之前,我会尝试像常规 GCE 虚拟机一样对其进行调试。另请检查cloud.google.com/appengine/docs/flexible/custom-runtimes/…。无论如何,为了简单起见,我将把它作为一个单独的问题提出。
    猜你喜欢
    • 2011-03-20
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2017-11-24
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多