简体   繁体   English

在 Cloud Run 上部署服务时,未使用最新版本

[英]When deploying a service on Cloud Run, the latest build is not being used

I'm using this command to submit the build:我正在使用此命令提交构建:

gcloud builds submit --tag gcr.io/[my-project]/[my-service]

This successfully submits the build and everything is correct in the Cloud Build tab in the GCP interface.这样就成功提交了构建,并且在 GCP 界面的 Cloud Build 选项卡中一切正常。

And this command to deploy:这个命令部署:

gcloud beta run deploy [my-service]
--service-account [service-account]@[my-project].iam.gserviceaccount.com
--image gcr.io/[my-project]/[my-service]:latest --cpu 2 --memory 8Gi
--timeout 59m59s --vpc-connector=pyston-vpc-connector
--vpc-egress=private-ranges-only 
--set-cloudsql-instances=[my-project]:europe-west2:[my-instance]

This does 'successfully' deploy the service, as in there are no errors.这确实“成功”部署了服务,因为没有错误。 However, it is not deploying using the latest build, it uses the last build submitted by someone else in my team.但是,它不是使用最新版本进行部署,而是使用我团队中其他人提交的最后一个版本。

I have tried deploying in the GCP interface as well but this led to the same outcome.我也尝试在 GCP 界面中进行部署,但这导致了相同的结果。

Any ideas on how t solve this?关于如何解决这个问题的任何想法?

Thanks!谢谢!

我在提交构建时指定了不正确的 Container Registry Repository,这意味着部署找不到最新的映像。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 部署到云运行时出现云构建错误 - Cloud build error when deploying to cloud run Cloud Run,当新的部署服务停止时 - Cloud Run, when new deploying service is stopping 用于在 CI 管道中部署云运行服务的 Google 云凭据 - Google cloud credentials for deploying cloud run service in CI pipeline 如何在 Cloud Run 中从 Cloud Build 自动部署最新映像 - How to auto deploy latest image from Cloud Build in Cloud Run 在云运行上部署时,服务帐户的权限“iam.serviceaccounts.actAs”被拒绝 - Permission 'iam.serviceaccounts.actAs' denied on service account when deploying on cloud run 尽管将更新的服务帐户信息传递给 admin.initializeApp,但在部署 Firebase Functions 时仍使用以前的 GCP 服务帐户 - Previous GCP service account being used when deploying Firebase Functions despite passing updated service account info to admin.initializeApp 为什么在使用 docker 部署云运行服务时出现 [INFO] Worker Exiting (pid: 2)? (在带有云代码扩展的 VSCode 上) - Why do I get [INFO] Worker Exiting (pid: 2) when deploying cloud run service with docker? (On VSCode with cloud code extension) 由于 VPC 连接器注释,部署 Cloud Run 服务失败 - Deploying Cloud Run Service fails because of VPC Connector annotation GCP:由于缺少标签“最新”,Cloud Run 预览构建失败 - GCP: Cloud Run preview build fails because of a missing tag "latest" 使用 Cloud Build 时,在不同的服务帐号下运行 Docker 容器 - Run a Docker container under a different service account when using Cloud Build
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM