[BUG] - COMPOSE_PROFILES=errors-only Doesn't Prevent Full Service Startup

[pierrejo]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

VERSION="25.1.0"

cd /opt/apps/sentry

git fetch

git checkout ${VERSION}

sudo ./install.sh

docker compose up --wait

Expected Result

The documentation states that setting COMPOSE_PROFILES=errors-only in the .env file should enable a minimal Sentry deployment focused on error tracking, minimizing resource usage. All the service use more than 90% of my RAM. Sentry seems to not working well in this configuration.

I was able to work around this by manually running the following command:

bash install.sh && docker compose --profile errors-only up --wait

Actual Result

After setting this variable and running the .install.sh script, all services (including those related to Traces, Profiles, Replays, etc.) appear to be started, leading to high RAM usage. This suggests the errors-only profile isn't being correctly applied during the standard installation process.

https://develop.sentry.dev/self-hosted/experimental/errors-only/

Product Area

Other

Link

No response

DSN

No response

Version

25.1.0

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[aldy505]

@hubertdeng123 Can you take a look over this?

[hubertdeng123]

I'm not able to reproduce this myself, setting COMPOSE_PROFILES=errors-only in the .env file works for me. What version of docker compose are you on? Maybe that could be impacting this. You could also try manually setting the COMPOSE_PROFILES env variable as well

[getsantry[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀