nodejs-getting-started: ERROR: (gcloud.app.deploy) Error Response: [13] An internal error occurred.
New project and it’s not deploying.
Do you want to continue (Y/n)? y
Beginning deployment of service [default]...
╔════════════════════════════════════════════════════════════╗
╠═ Uploading 0 files to Google Cloud Storage ═╣
╚════════════════════════════════════════════════════════════╝
File upload done.
Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [13] An internal error occurred.
From searching I’ve tried gcloud config set app/use_deprecated_preparation True
which does nothing
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 4
- Comments: 16 (4 by maintainers)
It would be great if gcloud deploy could tell us what might be the reason for not being able to deploy.
Three main reasons: Account Permissions, gcloud components, or invalid file types(.DS_Store or Mac Icons).
Hi, I’ve managed to resolve my issue thanks to your comment about Cloud Build API. I do have a billing account. I was using a service account, which previously had the following permissions:
Using the cloud console in the IAM section I added some more permissions for container builder so that it now has the following:
Ideally, I think instead of an internal error message, it’d be great if the gcloud output mentioned that it was a permissions error, as I managed to fix this in about 2 minutes once I started searching for Cloud Build API. I think this is more to do with the app engine deployment API response, rather than the gcloud command line tool, but something needs fixed somewhere for sure.
Thanks for your help!
Thanks a lot, we can reproduce (it occurs with newly created projects) and are investigating the issue.