-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Web container healthcheck does not consider SENTRY_BIND variable #3550
Comments
I have investigated this a bit on my own, if you change this line to use your custom port (in my case 9200), then it does boot up correctly. |
I still seem to get a bad gateway, probably due to this line in the nginx config |
The following lines in the relay container point to problems in ingestion:
|
Hey @Bart-Westenenk what was your |
I set it to |
Any news regarding this issue? Will this be picked up? Can I help out in some way? |
Self-Hosted Version
24.12.1
CPU Architecture
x86_64
Docker Version
27.4.1
Docker Compose Version
2.32.1
Machine Specification
Steps to Reproduce
SENTRY_BIND
variable using a.env.custom
file as documented in the docs../install.sh
docker compose --env-file .env.custom up -d
Expected Result
Expected the container to be healthy after booting up.
Actual Result
Output of running
docker compose --env-file .env.custom up -d
:Event ID
No response
The text was updated successfully, but these errors were encountered: