当前位置： 文江博客话题详情

麻烦构建和部署Docker容器以运行云

发布于 2025-01-23 20:11:49 字数 4831 浏览 0 评论 0原文

我已经进行了几个月的云运行服务。但是，我昨天试图对服务进行一些更新，突然间，我一直使用的脚本由于开始不再运行。

GCLOUD构建提交

我一直在使用以下命令来通过远程Docker容器来构建我的节点/NPM项目：

gcloud builds submit --tag gcr.io/PROJECT_ID/generator

我在与我的poffage.json同一目录中有一个dockerfile和.dockerignore。但是，昨天，我突然开始遇到一个错误，这些错误是使用 - 标签参数时需要一个dockerfile，并且图像不会构建。

经过一些研究后，我尝试将构建CNFIG

移至Gcloudbuild阶段。json，看起来像这样：

{
  "steps": [
    {
      "name": "gcr.io/cloud-builders/docker",
      "args": [
        "build",
        "-t",
        "gcr.io/PROJECT_ID/generator",
        "."
      ]
    }
  ]
}

我将构建脚本抓住了：

gcloud builds submit --config=./gcloudbuild-staging.json

这样做之后，容器将构建 - 或者尽我所能告诉。控制台输出看起来像：

------------------------------------------------- REMOTE BUILD OUTPUT --------------------------------------------------
starting build "8ca1af4c-d337-4349-959f-0000577e4528"

FETCHSOURCE
Fetching storage object: gs://PROJECT_ID/source/1650660913.623365-8a689bcf007749b7befa6e21ab9086dd.tgz#1650660991205773
Copying gs://PROJECT_ID/source/1650660913.623365-8a689bcf007749b7befa6e21ab9086dd.tgz#1650660991205773...
/ [0 files][    0.0 B/ 22.2 MiB]                                                
/ [1 files][ 22.2 MiB/ 22.2 MiB]                                                
-
Operation completed over 1 objects/22.2 MiB.
BUILD
Already have image (with digest): gcr.io/cloud-builders/docker
Sending build context to Docker daemon  785.4kB

Step 1/6 : FROM node:14-slim
14-slim: Pulling from library/node
8bd3f5a20b90: Pulling fs layer
3a665e454db5: Pulling fs layer
11fcaa1377c4: Pulling fs layer
bf0a7233d366: Pulling fs layer
0d4d73621610: Pulling fs layer
bf0a7233d366: Waiting
0d4d73621610: Waiting
3a665e454db5: Verifying Checksum
3a665e454db5: Download complete
bf0a7233d366: Verifying Checksum
bf0a7233d366: Download complete
8bd3f5a20b90: Verifying Checksum
8bd3f5a20b90: Download complete
0d4d73621610: Verifying Checksum
0d4d73621610: Download complete
11fcaa1377c4: Verifying Checksum
11fcaa1377c4: Download complete
8bd3f5a20b90: Pull complete
3a665e454db5: Pull complete
11fcaa1377c4: Pull complete
bf0a7233d366: Pull complete
0d4d73621610: Pull complete
Digest: sha256:9ea3dfdff723469a060d1fa80577a090e14ed28157334d649518ef7ef8ba5b9b
Status: Downloaded newer image for node:14-slim
 ---> 913d072dc4d9
Step 2/6 : WORKDIR /usr/src/app
 ---> Running in 96bc104b9501
Removing intermediate container 96bc104b9501
 ---> 3b1b05ea0470
Step 3/6 : COPY package*.json ./
 ---> a6eca4a75ddd
Step 4/6 : RUN npm ci --only=production
 ---> Running in 7e870db13a9b

> [email protected] postinstall /usr/src/app/node_modules/protobufjs
> node scripts/postinstall

added 237 packages in 7.889s
Removing intermediate container 7e870db13a9b
 ---> 6a86cc961a09
Step 5/6 : COPY . ./
 ---> 9e1f0f7a69a9
Step 6/6 : CMD [ "node", "index.js" ]
 ---> Running in d1b4d054a974
Removing intermediate container d1b4d054a974
 ---> 672075ef5897
Successfully built 672075ef5897
Successfully tagged gcr.io/PROJECT_ID/generator:latest
PUSH
DONE
------------------------------------------------------------------------------------------------------------------------
ID                                    CREATE_TIME                DURATION  SOURCE                                                                                                    IMAGES  STATUS
8ca1af4c-d337-4349-959f-0000577e4528  2022-04-22T20:56:31+00:00  31S       gs://PROJECT_ID/source/1650660913.623365-8a689bcf007749b7befa6e21ab9086dd.tgz  -       SUCCESS

在线日志中没有错误。

GCLOUD RUN部署

在这里是我用来部署容器的代码：

gcloud run deploy generator --image gcr.io/PROJECT_ID/generator --region=us-central1 --set-env-vars ENVIRONMENT=DEV

此的控制台输出是：

Deploying container to Cloud Run service [generator] in project [PROJECT_ID] region [us-central1]
✓ Deploying... Done.
  ✓ Creating Revision...
  ✓ Routing traffic...
Done.
Service [generator] revision [generator-00082-kax] has been deployed and is serving 100 percent of traffic.
Service URL: https://generator-SERVICE_ID-uc.a.run.app

运行控制台中也没有错误。它显示了部署，好像一切都很好。

问题

什么都没有改变。在本地，使用前端应用程序运行此服务，该应用程序可以访问它成功的结果。但是，我在firebase上托管的应用程序的登台版仍在表现，好像代码的旧版本处于活动状态。

我尝试的是，

  • 我确保正在测试和部署在同一git分支上，
  • 我完成了多个构建和部署，以防万一有某种fluke。
  • 我已经尝试使用GCLOUD命令将服务的流量更新为其最新修订版，
  • 我确保我的客户端应用使用正确的服务URL。它似乎没有更改，但无论如何我都会复制/粘贴它，以防万一

我上次成功部署是在2022年3月19日。由于我唯一完成的是更新我的所有WSL Linux应用程序 - 其中包括gcloud。我以前无法分辨出哪个版本，但我现在使用Google Cloud CLI的38.0.0。

我尝试搜索我的问题，但没有任何相关的内容。对于为什么所有这些都停止工作的原因，我完全没有收到任何错误。我可以提供任何建议或更多信息？

原文

I've had a couple Cloud Run services live for several months. However, I attempted to make some updates to a service yesterday, and suddenly the scripts I have been using since the beginning are no longer functioning.

gcloud build submit

I've been using the following command to build my node/npm project via the remote docker container:

gcloud builds submit --tag gcr.io/PROJECT_ID/generator

I have a dockerfile and .dockerignore in the same directory as my package.json from where I run this script. However, yesterday I suddenly started getting an error which read that a dockerfile is required when using the --tag parameter and the image would not build.

Tentative Solution

After some research, I tried moving my build cnfig into a gcloudbuild-staging.json, which looks like this:

{
  "steps": [
    {
      "name": "gcr.io/cloud-builders/docker",
      "args": [
        "build",
        "-t",
        "gcr.io/PROJECT_ID/generator",
        "."
      ]
    }
  ]
}

And I've chnaged my build script to:

gcloud builds submit --config=./gcloudbuild-staging.json

After doing this, the container will build - or as far as I can tell. The console output looks like this:

------------------------------------------------- REMOTE BUILD OUTPUT --------------------------------------------------
starting build "8ca1af4c-d337-4349-959f-0000577e4528"

FETCHSOURCE
Fetching storage object: gs://PROJECT_ID/source/1650660913.623365-8a689bcf007749b7befa6e21ab9086dd.tgz#1650660991205773
Copying gs://PROJECT_ID/source/1650660913.623365-8a689bcf007749b7befa6e21ab9086dd.tgz#1650660991205773...
/ [0 files][    0.0 B/ 22.2 MiB]                                                
/ [1 files][ 22.2 MiB/ 22.2 MiB]                                                
-
Operation completed over 1 objects/22.2 MiB.
BUILD
Already have image (with digest): gcr.io/cloud-builders/docker
Sending build context to Docker daemon  785.4kB

Step 1/6 : FROM node:14-slim
14-slim: Pulling from library/node
8bd3f5a20b90: Pulling fs layer
3a665e454db5: Pulling fs layer
11fcaa1377c4: Pulling fs layer
bf0a7233d366: Pulling fs layer
0d4d73621610: Pulling fs layer
bf0a7233d366: Waiting
0d4d73621610: Waiting
3a665e454db5: Verifying Checksum
3a665e454db5: Download complete
bf0a7233d366: Verifying Checksum
bf0a7233d366: Download complete
8bd3f5a20b90: Verifying Checksum
8bd3f5a20b90: Download complete
0d4d73621610: Verifying Checksum
0d4d73621610: Download complete
11fcaa1377c4: Verifying Checksum
11fcaa1377c4: Download complete
8bd3f5a20b90: Pull complete
3a665e454db5: Pull complete
11fcaa1377c4: Pull complete
bf0a7233d366: Pull complete
0d4d73621610: Pull complete
Digest: sha256:9ea3dfdff723469a060d1fa80577a090e14ed28157334d649518ef7ef8ba5b9b
Status: Downloaded newer image for node:14-slim
 ---> 913d072dc4d9
Step 2/6 : WORKDIR /usr/src/app
 ---> Running in 96bc104b9501
Removing intermediate container 96bc104b9501
 ---> 3b1b05ea0470
Step 3/6 : COPY package*.json ./
 ---> a6eca4a75ddd
Step 4/6 : RUN npm ci --only=production
 ---> Running in 7e870db13a9b

> [email protected] postinstall /usr/src/app/node_modules/protobufjs
> node scripts/postinstall

added 237 packages in 7.889s
Removing intermediate container 7e870db13a9b
 ---> 6a86cc961a09
Step 5/6 : COPY . ./
 ---> 9e1f0f7a69a9
Step 6/6 : CMD [ "node", "index.js" ]
 ---> Running in d1b4d054a974
Removing intermediate container d1b4d054a974
 ---> 672075ef5897
Successfully built 672075ef5897
Successfully tagged gcr.io/PROJECT_ID/generator:latest
PUSH
DONE
------------------------------------------------------------------------------------------------------------------------
ID                                    CREATE_TIME                DURATION  SOURCE                                                                                                    IMAGES  STATUS
8ca1af4c-d337-4349-959f-0000577e4528  2022-04-22T20:56:31+00:00  31S       gs://PROJECT_ID/source/1650660913.623365-8a689bcf007749b7befa6e21ab9086dd.tgz  -       SUCCESS

There are no errors in the online logs.

gcloud run deploy

Here is the code I use to deploy the container:

gcloud run deploy generator --image gcr.io/PROJECT_ID/generator --region=us-central1 --set-env-vars ENVIRONMENT=DEV

The console output for this is:

Deploying container to Cloud Run service [generator] in project [PROJECT_ID] region [us-central1]
✓ Deploying... Done.
  ✓ Creating Revision...
  ✓ Routing traffic...
Done.
Service [generator] revision [generator-00082-kax] has been deployed and is serving 100 percent of traffic.
Service URL: https://generator-SERVICE_ID-uc.a.run.app

No errors in the run console, either. It shows the deployment as if everything is fine.

The Problem

Nothing is changing. Locally, running this service with the front-end app which accesses it produces successful results. However, my staging version of the app hosted on Firebase is still acting as if the old version of the code is active.

What I've Tried

  • I've made sure I'm testing and deploying on the same git branch
  • I've done multiple builds and deployments in case there was some kind of fluke.
  • I've tried using the gcloud command to update a service's traffic to its latest revision
  • I've made sure my client app is using the correct service URL. It doesn't appear to have changed but I copy/pasted it anyway just in case

My last successful deployment was on March 19, 2022. Since them, the only thing I've done is update all my WSL linux apps - which would include gcloud. I couldn't tell what version I ws on before, but I'm now on 38.0.0 of the Google Cloud CLI.

I've tried searching for my issue but nothing relevant is coming up. I'm totally stumped as to why all of this has stopped working and I'm receiving no errors whatsoever. Any suggestions or further info I can provide?

如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论， 你可以免费 注册 一个本站的账号。

评论（1）

时光礼记 2025-01-30 20:11:49

gcloud构建提交应该（！？）继续与- tag，只要您的文件夹中有dockerfile，您'重新运行命令，或者您明确指定源文件夹。

我没有争议您收到一个错误，但是看到您使用的命令以及导致的错误会很有帮助。您不需要切换到构建配置文件。虽然这不是问题。

使用最新的作为标签值具有挑战性。该术语表明将使用最新版本的容器映像，但这通常是 不是会发生什么。当像Cloud Run这样的服务正在运行图像标记最新和开发人员要求运行的服务时，这尤其具有挑战性 - 开发人员知道的（！）是另一个图像 - 但也标记为<代码>最新。

就大多数服务而言，相同的标签意味着相同的图像，因此（！）可能是云运行没有找到其他图像，或者您没有为其提供不同的图像。我不清楚发生了哪种选择，但我相信您对最新的使用正在引起您的某些问题。

因此。...对于初学者，请考虑使用一个系统，在该系统中，每次创建一个新容器时，都可以使用唯一的标识符标记它。这样做的一种常见方法是使用提交哈希（因为每个提交都会改变）。另外，您可以使用容器的摘要（而不是标签）来引用图像版本。这需要形式{img}@sha256：{hash}的图像引用。

最后，gcloud run现在（始终有？ 可能出错。

流程以减少您的步骤，从而

gcloud builds submit should (!?) continue to work with --tag as long as there is a Dockerfile in the folder from which you're running the command or you explicitly specify a source folder.

I'm not disputing that you received an error but it would be helpful to see the command you used and the error that resulted. You shouldn't have needed to switch to a build config file. Although that isn't the problem.

Using latest as a tag value is challenging. The term suggests that the latest version of a container image will be used but this is often not what happens. It is particularly challenging when a service like Cloud Run is running an image tagged latest and a developer asks the service to run -- what the developer knows (!) is a different image -- but also tagged latest.

As far as most services are concerned, same tag means same image and so it's possible (!) either that Cloud Run is not finding a different image or you're not providing it with a different image. I'm unclear which alternative is occurring but I'm confident that your use of latest is causing some of your issues.

So.... for starters, please consider using a system in which every time you create a new container, you tag it with a unique identifier. A common way to do this is to use a commit hash (as these change with every commit). Alternatively you can use the container's digest (instead of a tag) to reference an image version. This requires image references of the form {IMG}@sha256:{HASH}.

Lastly, gcloud run now (has always?) supported deployment from source (folder) to running service (it does the Cloud Build process for you and deploys the result to Cloud Run. It may be worth using this flow to reduce your steps and thereby the possibility of error.

See: Deploying from source code

回复 原文
~没有更多了~

关于作者

一曲琵琶半遮面シ

暂无简介

文章
评论
27 人气
发私信

相关话题

更多

热门标签

操作系统 程序设计 IT运维 Linux系统管理 JavaScript 服务器应用 solaris C/C++ PHP Shell BSD Vue.js aix Oracle Python HTML 系统管理 HTML5 CSS 前端
更多

推荐作者

饮湿

文章 0 评论 0

明月

文章 0 评论 0

02

文章 0 评论 0

hs1283

文章 0 评论 0

风向决定发型

文章 0 评论 0

落花浅忆

文章 0 评论 0

更多

友情链接

文江博客
    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
    原文