【发布时间】：2021-05-04 16:12:11
【问题描述】：
我正在使用用 TypeScript 编写的 Firebase 函数，并希望尝试在 Cloud Run 上以尽可能少的更改运行代码。到目前为止，我发现的最佳解决方案是使用 buildpacks 将 Firebase 函数包装在 Docker 容器中，然后将其部署到 Cloud Run。它们支持 Google Cloud Functions，所以理论上应该是可以的。
我尝试关注演示 here 但没有运气。生成 buildpack 后，它会出现 command not found: firebase 错误，该错误来自启动脚本 (firebase serve --only functions)。我尝试将其更改为npx firebase...，但仍然出现相同的错误。
对解决这个问题有什么建议吗？
构建命令：pack build --builder=gcr.io/buildpacks/builder buildpack-my-functions
堆栈跟踪：
latest: Pulling from buildpacks/builder
Digest: sha256:5148ca194b65b8c7e771e878353e0c204d56a7c53947dcb5800bcc6507b51be1
Status: Image is up to date for gcr.io/buildpacks/builder:latest
v1: Pulling from buildpacks/gcp/run
Digest: sha256:ae69bbad23be8d56c4cedba0aaaa2a8f298bbc00abcab5922b40ca0014f00718
Status: Image is up to date for gcr.io/buildpacks/gcp/run:v1
0.9.3: Pulling from buildpacksio/lifecycle
Digest: sha256:bc253af2edf1577717618cb3a95f0f16bb18fc9e804efbcc1b85f657d931a757
Status: Image is up to date for buildpacksio/lifecycle:0.9.3
===> DETECTING
[detector] 3 of 5 buildpacks participating
[detector] google.nodejs.runtime 0.9.2
[detector] google.nodejs.npm 0.9.0
[detector] google.utils.label 0.0.1
===> ANALYZING
[analyzer] Restoring metadata for "google.nodejs.runtime:node" from app image
[analyzer] Restoring metadata for "google.nodejs.npm:npm" from cache
===> RESTORING
[restorer] Restoring data for "google.nodejs.runtime:node" from cache
[restorer] Restoring data for "google.nodejs.npm:npm" from cache
===> BUILDING
[builder] === Node.js - Runtime (google.nodejs.runtime@0.9.2) ===
[builder] Resolving Node.js version based on semver "10"
[builder] --------------------------------------------------------------------------------
[builder] Running "curl --fail --show-error --silent --location --get --data-urlencode range=10 http://semver.io/node/resolve"
[builder] 10.23.2Done "curl --fail --show-error --silent --location --get --data-ur..." (1.163948619s)
[builder] Using resolved runtime version from package.json: 10.23.2
[builder] Runtime cache hit, skipping installation.
[builder] === Node.js - NPM (google.nodejs.npm@0.9.0) ===
[builder] Installing application dependencies.
[builder] --------------------------------------------------------------------------------
[builder] Running "npm install --quiet (NODE_ENV=production)"
... other builder logs ...
[builder] Done "npm install --quiet (NODE_ENV=production)" (51.751284576s)
[builder] === Utils - Label Image (google.utils.label@0.0.1) ===
===> EXPORTING
[exporter] Reusing layer 'google.nodejs.runtime:node'
[exporter] Reusing layer 'google.nodejs.npm:env'
[exporter] Adding 1/1 app layer(s)
[exporter] Reusing layer 'launcher'
[exporter] Reusing layer 'config'
[exporter] Reusing layer 'process-types'
[exporter] Adding label 'io.buildpacks.lifecycle.metadata'
[exporter] Adding label 'io.buildpacks.build.metadata'
[exporter] Adding label 'io.buildpacks.project.metadata'
[exporter] Setting default process type 'web'
[exporter] *** Images (74d17285fd66):
[exporter] buildpack-my-functions
[exporter] Reusing cache layer 'google.nodejs.runtime:node'
[exporter] Reusing cache layer 'google.nodejs.npm:npm'
Successfully built image buildpack-my-functions
【问题讨论】：
-
你能分享一下buildpack log trace吗？这可能是因为 Buildpack 没有正确检测到您的代码类型和格式，ir 使用了错误的基础映像，因此您遇到了这个问题。
-
当然，我把它添加到问题中
标签： firebase google-cloud-functions google-cloud-run