Use internal SQLite3 database #81
Annotations
1 error and 7 warnings
|
Deploy to Cloud Run
failed to execute gcloud command `gcloud beta run deploy sepomex-pr67 --image us-central1-docker.pkg.dev/sepomex-365521/icalialabs-sepomex/sepomex@sha256:ba7beb12726afab4d4bc36165c90d6ee6874683550f1c27631dfa0f463251e2d --quiet --platform managed --region us-central1 --update-env-vars DATABASE_URL=postgres://%2Fcloudsql%2Fsepomex-365521%3Aus-central1%3Asepomex/sepomex_pr67,GOOGLE_CLOUD_PROJECT=sepomex-365521,DEPLOY_NAME=pr67 --update-secrets DATABASE_USERNAME=database-username:latest,DATABASE_PASSWORD=database-password:latest --revision-suffix 7e136db-1713972340 --allow-unauthenticated --add-cloudsql-instances sepomex-365521:us-central1:sepomex --min-instances 0 --service-account [email protected] --project sepomex-365521 --format json`: Deploying container to Cloud Run service [sepomex-pr67] in project [sepomex-365521] region [us-central1]
Deploying...
Setting IAM Policy..............done
Creating Revision............done
Routing traffic..............................................................................................................................................................................................failed
Deployment failed
ERROR: (gcloud.beta.run.deploy) Revision 'sepomex-pr67-7e136db-1713972340' 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. Logs for this revision might contain more information.
Logs URL: https://console.cloud.google.com/logs/viewer?project=sepomex-365521&resource=cloud_run_revision/service_name/sepomex-pr67/revision_name/sepomex-pr67-7e136db-1713972340&advancedFilter=resource.type%3D%22cloud_run_revision%22%0Aresource.labels.service_name%3D%22sepomex-pr67%22%0Aresource.labels.revision_name%3D%22sepomex-pr67-7e136db-1713972340%22
For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start
|
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/[email protected], google-github-actions/[email protected], google-github-actions/[email protected], bobheadxi/[email protected], google-github-actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Finalize the deployment state on Github
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Register Deploy Start on Github
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Register Deploy Start on Github
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Register Deploy Start on Github
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Authenticate to Google Cloud
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Authenticate to Google Cloud
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Loading