firebase-functions: [Error] V2 functions deployment fails with error in cloud run container service container fails to start

Hi. I’m sorry I missed this issue.

I re-read the issue thread, and common issue I see is that there are, to one degree or another, some initialization code that contribute to container instance not starting properly on cloud run.

For example, I can replicate the issue

Note that this isn’t chip dependent - the container image deployed to Google Cloud Functions v2 is built on Cloud Build and is not affected by your development machine. Here’s an example:

const functions = require("firebase-functions");
const { onRequest } = require("firebase-functions/v2/https");


const foo = functions.config("hello") // This will throw a runtime error on v2

module.exports = onRequest(
  { timeoutSeconds: 1200, region: ["europe-west1"] },
  (_req, res) => {
    res.status(200).send("OK");
  }
);

Note the use of functions.config - we do not support using functions config in v2 environment. Instead, we recommend that you use environment variables (https://firebase.google.com/docs/functions/config-env).

That being said, this is a very bad footgun. I will brainstorm with the team how we can improve the error message so that it’s clear exactly what’s going on during a function deploy.

Closing the issue as I think the original issue has been identified and resolved.

Same issue happened here. I’m using a MacBook Pro M1 and this page says:

Note: If you build your container image on a ARM based machine, then it might not work as expected when used with Cloud Run.

So I guess I’ll have to stick with Functions v1 for now.

Source code:

import { onRequest } from 'firebase-functions/v2/https'

export const helloworld = onRequest(
  {
    region: 'us-east1',
  },
  (request, response) => {
    response.status(200).send({ hello: 'world' })
  },
)

Output when deploying:

i  deploying functions
i  functions: ensuring required API cloudfunctions.googleapis.com is enabled...
i  functions: ensuring required API cloudbuild.googleapis.com is enabled...
✔  functions: required API cloudfunctions.googleapis.com is enabled
✔  functions: required API cloudbuild.googleapis.com is enabled
i  functions: ensuring required API artifactregistry.googleapis.com is enabled...
i  functions: ensuring required API run.googleapis.com is enabled...
i  functions: ensuring required API eventarc.googleapis.com is enabled...
i  functions: ensuring required API pubsub.googleapis.com is enabled...
i  functions: ensuring required API storage.googleapis.com is enabled...
✔  functions: required API eventarc.googleapis.com is enabled
✔  functions: required API artifactregistry.googleapis.com is enabled
✔  functions: required API run.googleapis.com is enabled
✔  functions: required API storage.googleapis.com is enabled
✔  functions: required API pubsub.googleapis.com is enabled
i  functions: preparing ./build/functions directory for uploading...
i  functions: packaged ./build/functions (56.65 KB) for uploading
i  functions: packaged ./build/functions (55.54 KB) for uploading
i  functions: ensuring required API cloudscheduler.googleapis.com is enabled...
✔  functions: required API cloudscheduler.googleapis.com is enabled
✔  functions: ./build/functions folder uploaded successfully
i  functions: creating Node.js 16 function helloworld(us-east1)...

Functions deploy had errors with the following functions:
        helloworld(us-east1)
i  functions: cleaning up build files...

Error: There was an error deploying functions
error Command failed with exit code 2.

Google Cloud Logging:

Could not create or update Cloud Run service helloworld, Container Healthcheck failed. Cloud Run error: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable. Logs for this revision might contain more information.

Versions: firebase-functions: v3.18.1 firebase-tools: v10.2.2

@gustavopch It’s wild considering how many companies and users use firebase functions. Would have thought someone from the team at google would have at least replied by now.

Also happened to me on intel chip

I posted on GCP functions framework issues board a while back there was at least some interaction. This lack of inactivity leaves me feeling like we’ve bet on the wrong stack here…

Fingers crossed we get an update and fix soon.

@clementdevos Thanks for the feedback!

Missing documentation is a clear oversight by us. I’ll see if we can add a snippet about this behavior for v2 runtime.

Tangent - on separating v1 and v2 functions; I think you might find the relatively-new codebase feature useful there. Let us know if we an help w/ anything!

I stumbled upon the same issue as @algoflows and after rereading the logs a couple of times, it occurred to me that I was getting the configuration of the function by calling functions.config which is not supported in functions v2. The error message is pretty clear on that:

Detailed stack trace: Error: functions.config() is no longer available
in Cloud Functions for Firebase v2. Please see the latest documentation
for information on how to transition to using environment variables

I hope this helps.

I got the same issue although I used v2 functions env reference like this. But I am not sure if it is because we have v1 and v2 in one repo. @taeold , having v1 and v2 together in one repo will impact that issue?