Opinie (Developing a REST API with Go and Cloud Run)

shital k. · Sprawdzono około 19 godzin temu

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

Taweechok L. · Sprawdzono około 21 godzin temu

Jeffrey H. · Sprawdzono 1 dzień temu

Gianmarco B. · Sprawdzono 1 dzień temu

Patrick L. · Sprawdzono 1 dzień temu

Vadim Z. · Sprawdzono 1 dzień temu

Varnita M. · Sprawdzono 2 dni temu

Nathaniel J. · Sprawdzono 2 dni temu

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.

Gabriela S. · Sprawdzono 2 dni temu

Emre D. · Sprawdzono 2 dni temu

Prathamesh S. · Sprawdzono 3 dni temu

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.

Gabriela S. · Sprawdzono 3 dni temu

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

Michael T. · Sprawdzono 3 dni temu

Maxi F. · Sprawdzono 3 dni temu

pooja j. · Sprawdzono 4 dni temu

Arul Sahaya Selvam J. · Sprawdzono 4 dni temu

Mohamad Ridwan M. · Sprawdzono 4 dni temu

Leonard S. · Sprawdzono 4 dni temu

Deployment of the container does not work. ERROR: (gcloud.run.deploy) Revision 'rest-api-00006-vp2' 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.

Robert B. · Sprawdzono 4 dni temu

Yemi F. · Sprawdzono 4 dni temu

VINOD H. · Sprawdzono 4 dni temu

Saudagar S. · Sprawdzono 5 dni temu

Ashish N. · Sprawdzono 5 dni temu

Deployment was always failing in both version. Log or troubleshooting guidelines were not clear.

Pradip G. · Sprawdzono 5 dni temu

Maxwell A. · Sprawdzono 5 dni temu