How to fix gcloud app deployment error Cloud build failed. Failure status: UNKNOWN?
up vote
-1
down vote
favorite
I am trying deploy my node.js project into Google Cloud. It works fine on localhost but when I try to deploy into GCP I am getting an error:
ERROR: (gcloud.app.deploy) Cloud build failed. Failure status:
UNKNOWN: Error Response: [2] Build failed .
node.js deployment gcloud
edited Nov 11 at 15:38
Graham
3,451123558
asked Nov 11 at 10:33
Arun Gavimath
32
|
show 6 more comments
up vote
-1
down vote
favorite
I am trying deploy my node.js project into Google Cloud. It works fine on localhost but when I try to deploy into GCP I am getting an error:
ERROR: (gcloud.app.deploy) Cloud build failed. Failure status:
UNKNOWN: Error Response: [2] Build failed .
node.js deployment gcloud
edited Nov 11 at 15:38
Graham
3,451123558
asked Nov 11 at 10:33
Arun Gavimath
32
The line before the last of the error message tells you to check the build logs for more details. Please, take a look and if you can't figure it out, paste the relevant part of the log file here.
– lependu
Nov 11 at 10:35
i coudn't figure out from the log file. Here is complete log file.
– Arun Gavimath
Nov 11 at 11:02
starting build "74fce248-f0a2-4408-89ad-f4408d4068ed" FETCHSOURCE Fetching storage object: gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575 Copying gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575... / [1 files][ 1.4 MiB/ 1.4 MiB] Operation completed over 1 objects/1.4 MiB. BUILD
– Arun Gavimath
Nov 11 at 11:05
Starting Step #0 Step #0: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Digest: sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Checking for Node.js. Step #0: WARNING: Your package.json does not specify a supported Node.js version. Please pin your application to a major version of the Node.js runtime.
– Arun Gavimath
Nov 11 at 11:06
Next time paste the log file into your original question. And format it with code (CTRL+K)
– lependu
Nov 11 at 11:06
|
show 6 more comments
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I am trying deploy my node.js project into Google Cloud. It works fine on localhost but when I try to deploy into GCP I am getting an error:
ERROR: (gcloud.app.deploy) Cloud build failed. Failure status:
UNKNOWN: Error Response: [2] Build failed .
node.js deployment gcloud
edited Nov 11 at 15:38
Graham
3,451123558
asked Nov 11 at 10:33
Arun Gavimath
32
I am trying deploy my node.js project into Google Cloud. It works fine on localhost but when I try to deploy into GCP I am getting an error:
ERROR: (gcloud.app.deploy) Cloud build failed. Failure status:
UNKNOWN: Error Response: [2] Build failed .
node.js deployment gcloud
node.js deployment gcloud
edited Nov 11 at 15:38
Graham
3,451123558
asked Nov 11 at 10:33
Arun Gavimath
32
edited Nov 11 at 15:38
Graham
3,451123558
asked Nov 11 at 10:33
Arun Gavimath
32
edited Nov 11 at 15:38
Graham
3,451123558
edited Nov 11 at 15:38
Graham
3,451123558
edited Nov 11 at 15:38
Graham
3,451123558
3,451123558
asked Nov 11 at 10:33
Arun Gavimath
32
asked Nov 11 at 10:33
Arun Gavimath
32
asked Nov 11 at 10:33
Arun Gavimath
32
32
The line before the last of the error message tells you to check the build logs for more details. Please, take a look and if you can't figure it out, paste the relevant part of the log file here.
– lependu
Nov 11 at 10:35
i coudn't figure out from the log file. Here is complete log file.
– Arun Gavimath
Nov 11 at 11:02
starting build "74fce248-f0a2-4408-89ad-f4408d4068ed" FETCHSOURCE Fetching storage object: gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575 Copying gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575... / [1 files][ 1.4 MiB/ 1.4 MiB] Operation completed over 1 objects/1.4 MiB. BUILD
– Arun Gavimath
Nov 11 at 11:05
Starting Step #0 Step #0: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Digest: sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Checking for Node.js. Step #0: WARNING: Your package.json does not specify a supported Node.js version. Please pin your application to a major version of the Node.js runtime.
– Arun Gavimath
Nov 11 at 11:06
Next time paste the log file into your original question. And format it with code (CTRL+K)
– lependu
Nov 11 at 11:06
|
show 6 more comments
The line before the last of the error message tells you to check the build logs for more details. Please, take a look and if you can't figure it out, paste the relevant part of the log file here.
– lependu
Nov 11 at 10:35
i coudn't figure out from the log file. Here is complete log file.
– Arun Gavimath
Nov 11 at 11:02
starting build "74fce248-f0a2-4408-89ad-f4408d4068ed" FETCHSOURCE Fetching storage object: gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575 Copying gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575... / [1 files][ 1.4 MiB/ 1.4 MiB] Operation completed over 1 objects/1.4 MiB. BUILD
– Arun Gavimath
Nov 11 at 11:05
Starting Step #0 Step #0: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Digest: sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Checking for Node.js. Step #0: WARNING: Your package.json does not specify a supported Node.js version. Please pin your application to a major version of the Node.js runtime.
– Arun Gavimath
Nov 11 at 11:06
Next time paste the log file into your original question. And format it with code (CTRL+K)
– lependu
Nov 11 at 11:06
The line before the last of the error message tells you to check the build logs for more details. Please, take a look and if you can't figure it out, paste the relevant part of the log file here.
– lependu
Nov 11 at 10:35
The line before the last of the error message tells you to check the build logs for more details. Please, take a look and if you can't figure it out, paste the relevant part of the log file here.
– lependu
Nov 11 at 10:35
i coudn't figure out from the log file. Here is complete log file.
– Arun Gavimath
Nov 11 at 11:02
i coudn't figure out from the log file. Here is complete log file.
– Arun Gavimath
Nov 11 at 11:02
starting build "74fce248-f0a2-4408-89ad-f4408d4068ed" FETCHSOURCE Fetching storage object: gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575 Copying gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575... / [1 files][ 1.4 MiB/ 1.4 MiB] Operation completed over 1 objects/1.4 MiB. BUILD
– Arun Gavimath
Nov 11 at 11:05
starting build "74fce248-f0a2-4408-89ad-f4408d4068ed" FETCHSOURCE Fetching storage object: gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575 Copying gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575... / [1 files][ 1.4 MiB/ 1.4 MiB] Operation completed over 1 objects/1.4 MiB. BUILD
– Arun Gavimath
Nov 11 at 11:05
Starting Step #0 Step #0: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Digest: sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Checking for Node.js. Step #0: WARNING: Your package.json does not specify a supported Node.js version. Please pin your application to a major version of the Node.js runtime.
– Arun Gavimath
Nov 11 at 11:06
Starting Step #0 Step #0: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Digest: sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Checking for Node.js. Step #0: WARNING: Your package.json does not specify a supported Node.js version. Please pin your application to a major version of the Node.js runtime.
– Arun Gavimath
Nov 11 at 11:06
Next time paste the log file into your original question. And format it with code (CTRL+K)
– lependu
Nov 11 at 11:06
Next time paste the log file into your original question. And format it with code (CTRL+K)
– lependu
Nov 11 at 11:06
|
show 6 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Your build fails because it can not build bcrypt. Solution could be to remove it from the package json. Which you can do, because you already use bcrypt-nodejs which does the same thing and it is pure js, so it does not require to install native add-ons.
answered Nov 11 at 12:33
lependu
659314
yes.Thanks a lot. Now deployment was successfull. But i want to know what was the problem with bcrypt module. 2 days back i had deployed the same package.json.
– Arun Gavimath
Nov 11 at 12:56
No worries. Please don't forget to accept the answer. see this issue for details.
– lependu
Nov 11 at 13:00
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Your build fails because it can not build bcrypt. Solution could be to remove it from the package json. Which you can do, because you already use bcrypt-nodejs which does the same thing and it is pure js, so it does not require to install native add-ons.
answered Nov 11 at 12:33
lependu
659314
yes.Thanks a lot. Now deployment was successfull. But i want to know what was the problem with bcrypt module. 2 days back i had deployed the same package.json.
– Arun Gavimath
Nov 11 at 12:56
No worries. Please don't forget to accept the answer. see this issue for details.
– lependu
Nov 11 at 13:00
add a comment |
up vote
0
down vote
accepted
Your build fails because it can not build bcrypt. Solution could be to remove it from the package json. Which you can do, because you already use bcrypt-nodejs which does the same thing and it is pure js, so it does not require to install native add-ons.
answered Nov 11 at 12:33
lependu
659314
yes.Thanks a lot. Now deployment was successfull. But i want to know what was the problem with bcrypt module. 2 days back i had deployed the same package.json.
– Arun Gavimath
Nov 11 at 12:56
No worries. Please don't forget to accept the answer. see this issue for details.
– lependu
Nov 11 at 13:00
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Your build fails because it can not build bcrypt. Solution could be to remove it from the package json. Which you can do, because you already use bcrypt-nodejs which does the same thing and it is pure js, so it does not require to install native add-ons.
answered Nov 11 at 12:33
lependu
659314
Your build fails because it can not build bcrypt. Solution could be to remove it from the package json. Which you can do, because you already use bcrypt-nodejs which does the same thing and it is pure js, so it does not require to install native add-ons.
answered Nov 11 at 12:33
lependu
659314
edited Nov 11 at 12:40
answered Nov 11 at 12:33
lependu
659314
answered Nov 11 at 12:33
lependu
659314
answered Nov 11 at 12:33
lependu
659314
659314
yes.Thanks a lot. Now deployment was successfull. But i want to know what was the problem with bcrypt module. 2 days back i had deployed the same package.json.
– Arun Gavimath
Nov 11 at 12:56
No worries. Please don't forget to accept the answer. see this issue for details.
– lependu
Nov 11 at 13:00
add a comment |
yes.Thanks a lot. Now deployment was successfull. But i want to know what was the problem with bcrypt module. 2 days back i had deployed the same package.json.
– Arun Gavimath
Nov 11 at 12:56
No worries. Please don't forget to accept the answer. see this issue for details.
– lependu
Nov 11 at 13:00
yes.Thanks a lot. Now deployment was successfull. But i want to know what was the problem with bcrypt module. 2 days back i had deployed the same package.json.
– Arun Gavimath
Nov 11 at 12:56
yes.Thanks a lot. Now deployment was successfull. But i want to know what was the problem with bcrypt module. 2 days back i had deployed the same package.json.
– Arun Gavimath
Nov 11 at 12:56
No worries. Please don't forget to accept the answer. see this issue for details.
– lependu
Nov 11 at 13:00
No worries. Please don't forget to accept the answer. see this issue for details.
– lependu
Nov 11 at 13:00
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53247869%2fhow-to-fix-gcloud-app-deployment-error-cloud-build-failed-failure-status-unkno%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The line before the last of the error message tells you to check the build logs for more details. Please, take a look and if you can't figure it out, paste the relevant part of the log file here.
– lependu
Nov 11 at 10:35
i coudn't figure out from the log file. Here is complete log file.
– Arun Gavimath
Nov 11 at 11:02
starting build "74fce248-f0a2-4408-89ad-f4408d4068ed" FETCHSOURCE Fetching storage object: gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575 Copying gs://staging.whatmate-nodejs.appspot.com/us.gcr.io/whatmate-nodejs/appengine/default.20181111t153759:latest#1541931249630575... / [1 files][ 1.4 MiB/ 1.4 MiB] Operation completed over 1 objects/1.4 MiB. BUILD
– Arun Gavimath
Nov 11 at 11:05
Starting Step #0 Step #0: Pulling image: gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Digest: sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Status: Downloaded newer image for gcr.io/gcp-runtimes/nodejs/gen-dockerfile@sha256:98d9069aa67a763de7e6fd81c41f937b171917f1e83a1afce30fc3d618a3c110 Step #0: Checking for Node.js. Step #0: WARNING: Your package.json does not specify a supported Node.js version. Please pin your application to a major version of the Node.js runtime.
– Arun Gavimath
Nov 11 at 11:06
Next time paste the log file into your original question. And format it with code (CTRL+K)
– lependu
Nov 11 at 11:06