Closed hubertdeng123 closed 2 months ago
Possible solution from Friberg on discord:
https://discord.com/channels/621778831602221064/796028405833007104/1235624852564611106
Didn't encountered the migration error when not using the alpine image (meaning continue using the debian image)
diff --git a/docker-compose.yml b/docker-compose.yml
index 9cc58dd..cb800ad 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -132,7 +132,7 @@ services:
postgres:
<<: *restart_policy
# Using the same postgres version as Sentry dev for consistency purposes
- image: "postgres:14.11-alpine"
+ image: "postgres:14.11"
healthcheck:
<<: *healthcheck_defaults
# Using default user "postgres" from sentry/sentry.conf.example.py or value of POSTGRES_USER if provided
What @aldy505 posted worked for me as well
note you can create a docker.override.yml
file instead of editing docker-compose.yml directly (which is tracked)
docker.override.yml
services:
postgres:
# https://github.com/getsentry/self-hosted/issues/3014
image: "postgres:14.11"
Ref: #3027
Going to close this due to https://github.com/getsentry/self-hosted/pull/3116
Self-Hosted Version
24.4.2
CPU Architecture
x86_64
Docker Version
n/a
Docker Compose Version
n/a
Steps to Reproduce
Upgrading to 24.4.2+ is giving some users issues. This is taken from discord
Expected Result
no error
Actual Result
error
Event ID
No response