Replies: 6 comments 2 replies
-
|
I followed the guide exactly thats lisited on hono |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mstibbard, can you look at whether the web instruction is correct? |
Beta Was this translation helpful? Give feedback.
-
|
The error suggests you provided your own container (by including a Dockerfile). If you did would you please share its contents? To serve via port 8080 your Dockerfile requires the line Not providing a Dockerfile results in a Google-provided buildpack being used which exposes 8080 by default. EDIT: I just re-tested the guide and it worked without any deviations. Did you remember to update the port in |
Beta Was this translation helpful? Give feedback.
-
|
I did not provide any docker file, I just followed the instructions and
tried to deploy it.
I can share the repo if you want to currently it's on local
…On Wed, 30 Apr 2025, 3:43 pm Stibbs, ***@***.***> wrote:
The error suggests you provided your own container (by including a
Dockerfile). If you did would you please share its contents?
—
Reply to this email directly, view it on GitHub
<#4117 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANMR7CICLCFRJFKLJYAE7HL24CO45AVCNFSM6AAAAAB4CYZHOKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJZGE2DKNQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
On it thanks for helping
…On Wed, 30 Apr 2025, 4:06 pm Stibbs, ***@***.***> wrote:
I am happy to take a look if you share it
—
Reply to this email directly, view it on GitHub
<#4117 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANMR7CM6HYPQCDBAK3PZKZD24CRULAVCNFSM6AAAAAB4CYZHOKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJZGE3DINI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Worked sorry my bad missed the part thanks @mstibbard |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
(gcloud.run.deploy) Revision 'my-app' 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.
For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start
Beta Was this translation helpful? Give feedback.
All reactions