Skip to content

Migrate plugins to cloudrun #36

Migrate plugins to cloudrun

Migrate plugins to cloudrun #36

Triggered via push November 22, 2024 02:02
Status Failure
Total duration 3m 6s
Artifacts

gcp_plugins.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error
deploy
google-github-actions/deploy-cloudrun failed with: failed to execute gcloud command `gcloud run deploy plugins --image gcr.io/based-hardware-dev/plugins --update-labels ^,^managed-by=github-actions,commit-sha=39d1eefc2f3e3c69465b7eee0f2b31320abb40c2 --format json --region us-central1`: Deploying container to Cloud Run service [plugins] in project [based-hardware-dev] region [us-central1] Deploying... Creating Revision..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................failed Deployment failed ERROR: (gcloud.run.deploy) Revision 'plugins-00002-njv' is not ready and cannot serve traffic. The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable within the allocated timeout. This can happen when the container port is misconfigured or if the timeout is too short. The health check timeout can be extended. Logs for this revision might contain more information. Logs URL: https://console.cloud.google.com/logs/viewer?project=based-hardware-dev&resource=cloud_run_revision/service_name/plugins/revision_name/plugins-00002-njv&advancedFilter=resource.type%3D%22cloud_run_revision%22%0Aresource.labels.service_name%3D%22plugins%22%0Aresource.labels.revision_name%3D%22plugins-00002-njv%22 For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start