Go と Cloud Run を使用した REST API の開発 のレビュー

王 亭宇 · 約4時間前にレビュー済み

DEMOLIN DAMIEN · 約11時間前にレビュー済み

Nice

Pardhi Ranu · 約13時間前にレビュー済み

Ichsan Nurjaman R Mochamad · 約13時間前にレビュー済み

use debian 12 instead of 10

Bulle Hieronymus · 約17時間前にレビュー済み

CE Shameer · 1日前にレビュー済み

Shu Heng. Thong · 1日前にレビュー済み

Khatri Chetan · 1日前にレビュー済み

Hati Edwin · 1日前にレビュー済み

Evangelio Arnel · 2日前にレビュー済み

隠岐 仁壱 · 3日前にレビュー済み

Palanisamy Mythili · 3日前にレビュー済み

kurdane shital · 4日前にレビュー済み

I got this problem when I try to deploy. Revision 'rest-api-00001-778' 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: Open Cloud Logging For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start

Limsakul Taweechok · 4日前にレビュー済み

Hui Jeffrey · 4日前にレビュー済み

Barca Gianmarco · 4日前にレビュー済み

Lorenz Patrick · 4日前にレビュー済み

Zaripov Vadim · 5日前にレビュー済み

Makrariya Varnita · 5日前にレビュー済み

Joseph Nathaniel · 5日前にレビュー済み

Both deployments failed. I have emailed support about this. Also, the Cloud Console did not let me select a region for my database, so I had to use the command line to create it, and then when I was told to create a new endpoint, it contained the string "[hash]". The second deployment failed just like the first one, there was never a service listening on port 8080. At least the checks did not take that into account and I was able to finish the lab, but this lab is so broken it is hard to derive any useful knowledge from it.

Steren Gabriela · 5日前にレビュー済み

Duzgun Emre · 5日前にレビュー済み

Sutar Prathamesh · 5日前にレビュー済み

I was unable to complete this lab. First, I had a problem with the auth token, which I was able to fix by logging in again. Then I was able to build my project, but I was unable to deploy it, as I kept getting this error message: "ERROR: (gcloud.run.deploy) Revision 'rest-api-00001-8d9' 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." I was unable to find anything useful in the logs. I figured it might be another authorization issue, but I couldn't find what needed to be authorized or how. I tried the lab again with a different user and did not have the first auth token issue, but I was still unable to deploy the project.

Steren Gabriela · 6日前にレビュー済み

The docker image is missing a glibc dependency. I needed to change the base image from gcr.io/distroless/base-debian10 to gcr.io/distroless/base-debian12 to fix the issue

Timblin Michael · 6日前にレビュー済み