TL;DR - Deployments are about to get faster; you don’t need to do a thing.
The App Engine Flexible Environment (previously know as Managed VMs) has always used Docker to package and run your App Engine FE applications. At first we required developers to install Docker, and build containers locally before publishing to App Engine. Last year we improved that process by automatically provisioning a virtual machine in your project, and performing the Docker build and push during deployment - eliminating the need to have Docker installed locally.
In the next release of the Google Cloud SDK, we’re making it even better by switching all Flexible Environment builds to our shiny new service, Google Cloud Container Builder. Container Builder provides a fast and secure way to build Docker images and publish them to Google Container Registry.
You don’t need to do anything to start using the new service. The only change you should notice is faster builds and deployments. If you do run into problems, please let us know by responding to the thread! You can always fall back to the in-project VM model by setting the app/use_cloud_build flag in gcloud to false:
gcloud config set app/use_cloud_build true|false
We recognize that build time and reliability is important for App Engine FE, and we’re hoping this change makes everyone's lives just a little easier.
You received this message because you are subscribed to the Google Groups "google-cloud-sdk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-cloud-sdk.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sdk/afca56a8-0f61-431d-ac4c-efd7cbe52dd8%40googlegroups.com.
Our deployment is failing with this:ERROR: (gcloud.preview.app.deploy) Error Response:  DEADLINE_EXCEEDEDAny tips on fix/workaround for that?Here's the tail end of the deployment messages:-----------
Successfully built 78753090e089
The push refers to a repository [appengine.gcr.io/gcloud/<appid>.<module>.<version>] (len: 1)
Sending image list
Pushing repository appengine.gcr.io/gcloud/camio-test.default.mongoose (1 tags)
Image 4bfc20f0ed66 already pushed, skipping
Image 3bc7cdb36864 already pushed, skipping
Image 096d9403d234 already pushed, skipping
ERROR: (gcloud.preview.app.deploy) Error Response:  DEADLINE_EXCEEDED
(1) Mar 27 01:40:14 Pulling GAE_FULL_APP_CONTAINER: [...]
(1) Mar 27 01:41:30 Done pulling app container
(2) Mar 27 01:40:01 Pulling GAE_FULL_APP_CONTAINER: [...]
(2) Mar 27 01:40:37 Done pulling app container
(1) Mar 27 01:53:07 Pulling GAE_FULL_APP_CONTAINER: [...]
(1) Mar 27 01:53:50 Done pulling app container(2) Mar 27 01:53:12 Pulling GAE_FULL_APP_CONTAINER: [...]
(2) Mar 27 01:53:51 Done pulling app container
We deploy go based runtimes (using the appengine runtime, not a custom one) and builds have gotten significantly slower and less reliable for us. Setting "use_cloud_build" to false doesn't seem to make a difference.Until this most recent change we were using appcfg.py to deploy our mvms, so I am comparing that process to using gcloud preview app deploy. They now take 5-10 minutes each, and fail around 30% of the time.Erik
Unless you wrestle directly with the REST API of the Container Builder.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sdk/7bce4af2-b290-4c7d-85a1-50f3fbe654b9%40googlegroups.com.