-
Notifications
You must be signed in to change notification settings - Fork 141
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
Slack notifier fails to deploy because it doesn't listen to port 8080 #186
Comments
same problem |
@vicpadilla can you help? |
@vicpadilla I'm also having the same issue. |
Same Issue here, has anyone figured out a fix or work around? I've tried using older images, but haven't |
It seems like the requirement for the 8080 came without fixing the code. I don't know Go but it seems like there is no part in the code that asks for port 8080. My idea is to ask ChatGPT to translate that Go code into Python and fix what's missing. If someone tries this path let know. Too busy at the moment. |
Normally, this error shows up when the provided config yaml is incorrect and the notifier fails to start. You can find more details by going to the Cloud Run page (https://console.cloud.google.com/run) and accessing the container logs. One possible misconfiguration is that the json template file is not present in GCS. The provided yaml example specifies such file as If it fails after that fix, please provide some details from the container logs. |
@vicpadilla with your hint I discovered that logs are complaining about:
So you were right, a typo in the config yaml but the error message was confusing for me. Thanks |
I'm following steps in https://cloud.google.com/build/docs/configuring-notifications/configure-slack but on step 9, when I run the command:
(hiding my own project id in the example above)
it fails to deploy because it says that the container is not listening in port 8080. This is the message I get:
Could it be that current image is broken?
The text was updated successfully, but these errors were encountered: