New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set hostname to 0.0.0.0 #54342
set hostname to 0.0.0.0 #54342
Conversation
Set hostname to 0.0.0.0 to avoid deployment failing on Google cloud run
set hostname to 0.0.0.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority |
---|---|---|
Passed | Secrets | 0 0 0 0 |
I have added a healthcheck. It worked before the change. Now the healthcheck stays in the status (health: starting) for almost two minutes. after that the docker container is (unhealthy). |
this breaks my Next Auth flow also, as I described here: nextauthjs/next-auth#8535 somehow the hostname is my container private IP and not its hostname So I have to downgrade from |
When I try to deploy to Google Cloud Run it fails after some investigation I saw this line in
.next/standalone/server.js
This some how make this log when i run docker
I don't know why it's logging this address even if the server running on localhost.
So this my fix
Set hostname to 0.0.0.0 to avoid deployment failing on Google cloud run.