Can't make a new NodeJS App Deploy

Paulo Freitas

unread,

Jan 22, 2019, 6:58:38 PM1/22/19

to Google App Engine

Hello guys,

I have a nodejs service running in the AppEngine for a while. But today, now, I tried to do a new deploy, `gcloud app deploy` and get a constant build error with a link to the log bellow, in itallic.
Anyone with the same issue? Does anyone has any clue on how to solve it?

att,

Paulo Freitas

Log here

starting build "3f82f9df-292c-4956-9558-43dcbc1400fa" FETCHSOURCE BUILD Starting Step #0 - "fetcher" Step #0 - "fetcher": Already have image (with digest): gcr.io/cloud-builders/gcs-fetcher Step #0 - "fetcher": Fetching manifest gs://staging.small-talk-3972f.appspot.com/ae/1081fb4b-8d15-4cda-a21c-e7a42a8a0e3d/manifest.json. Step #0 - "fetcher": Processing 1785 files. Step #0 - "fetcher": ****************************************************** Step #0 - "fetcher": Status: SUCCESS Step #0 - "fetcher": Started: 2019-01-22T18:35:38Z Step #0 - "fetcher": Completed: 2019-01-22T18:35:41Z Step #0 - "fetcher": Requested workers: 200 Step #0 - "fetcher": Actual workers: 200 Step #0 - "fetcher": Total files: 1785 Step #0 - "fetcher": Total retries: 0 Step #0 - "fetcher": GCS timeouts: 0 Step #0 - "fetcher": MiB downloaded: 5.93 MiB Step #0 - "fetcher": MiB/s throughput: 2.57 MiB/s Step #0 - "fetcher": Time for manifest: 322.05 ms Step #0 - "fetcher": Total time: 2.65 s Step #0 - "fetcher": ****************************************************** Finished Step #0 - "fetcher" Starting Step #1 - "builder" Step #1 - "builder": Pulling image: gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found Step #1 - "builder": Error response from daemon: manifest for gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00 not found ERROR: failed to pull because we ran out of retries. ERROR ERROR: build step 1 "gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00" failed: error pulling build step 1 "gcr.io/gae-runtimes/nodejs8_app_builder:nodejs8_20190118_8_15_0_RC00": exit status 1

George (Cloud Platform Support)

unread,

Jan 23, 2019, 4:08:33 PM1/23/19

to Google App Engine

Hello Paulo,

More information is needed to start our investigation properly. What steps have you undertaken prior to running this command? Have you modified anything in your application's code or app.yaml configuration file?

As a first step, you may consider running 'gcloud components update', and then trying to run gcloud init again.

After doing so, what is the output from the following commands?

gcloud info

gcloud app deploy --verbosity=debug

All sensitive information should be deleted or overwritten from replies, to safeguard your privacy.

A copy of your app.yaml file, sensitive information redacted out, is also needed, enabling us to recreate your environment in view of eventual error reproduction.

Jason Collins

unread,

Jan 23, 2019, 4:55:09 PM1/23/19

to Google App Engine

This should be fixed as of yesterday afternoon (Pacific Time). Please let us know if you are still seeing this issue.

Paulo Freitas

unread,

Jan 24, 2019, 10:27:33 AM1/24/19

to google-a...@googlegroups.com

This was indeed fixed. Earlier this day I was able to deploy successfully.

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/qPLsv2VbENg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/51ec0dad-fe1b-4e13-8ad7-12c2703670dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Paulo Freitas

unread,

Jan 24, 2019, 10:27:33 AM1/24/19

to Google App Engine

Thanks for your attention,

But as Jason Collins mentioned before, this was already fixed "by itself".

Reply all

Reply to author

Forward