Sourcegraph self-hosted on Docker Compose upgrade notes
Sourcegraph Cloud customers are automatically updated with the latest changes.
This page lists the changes that are relevant for upgrading Sourcegraph on Docker Compose.
For upgrade procedures or general info about sourcegraph versioning see the links below:
Attention: These notes may contain relevant information about the infrastructure update such as resource requirement changes or versions of dependencies (Docker, Docker Compose, externalized databases).
If the notes indicate a patch release exists, target the highest one.
7.1.0
- The bundled Jaeger instance has been upgraded from v1 to v2.16.0. Jaeger v2 replaces all legacy CLI flags with an OpenTelemetry Collector-style YAML configuration file. Any custom Jaeger CLI flags in your
docker-compose.override.yamlmust be replaced by mounting a custom YAML configuration file. OTLP receiver ports have changed to the standard4317(gRPC) and4318(HTTP), and a new health check port13133has been added. See [PR 1369] for details.
6.3.2692
- Grafana's port 3370 is no longer open by default for unauthenticated access for Docker Compose and Pure Docker deployments. Admins can still access Grafana by logging in to their Sourcegraph instance, navigating to the Site Admin page, then clicking Monitoring from the left navigation menu. If customers require port 3370 to be open, see [PR 1204] for insight on how to add this port to their
docker-compose.override.yamlfile.
6.2.2553
Known issues
Customers running Sourcegraph versions prior to v6.2.2553 and using the Sourcegraph provided PostgreSQL containers may encounter PostgreSQL collation version mismatch warnings after upgrading to more recent Sourcegraph versions due to an underlying glibc version update.
When logging into the database via psql or similar tools you may see the following warning:
Warning: database "sg" has a collation version mismatch DETAIL: The database was created using collation version 2.40, but the operating system provides version 2.41.
Mismatched collation versions can lead to database index corruption if left unchecked.
Affected services
- pgsql container
- codeintel-db container
- codeinsights-db container
Only self-hosted customers using the Sourcegraph provided PostgreSQL container images are affected.
Self-hosted customers using external databases, such as AWS RDS, GCP CloudSQL, or another self-managed solution are NOT affected.
See our PostgreSQL collation version mismatch resolution notes for more details.
6.0.0
- Sourcegraph 6.0.0 no longer supports PostgreSQL 12, admins must upgrade to PostgreSQL 16. See our postgres 12 end of life notice! As well as supporting documentation and advisements on how to upgrade.
5.10.1164
- This release resolves an issue in the v5.10.0 release which prevented multiversion upgrades from working. You may now target
v5.10.1164using migrator'supgradecommand.
Note: For versions prior to 6.12.0, you could also use autoupgrade by setting the environment variable
SRC_AUTOUPGRADE_IGNORE_DRIFT=trueon thefrontendcontainer. Autoupgrade has been removed in Sourcegraph 6.12.0 and later.
5.10.0
Warning: Admins are advised to upgrade directly to v5.10.1164 circumventing this release.
Warning: This release updates the database container images from Postgres 12 to Postgres 16, and begins using Wolfi based images. Customers are advised to take a database backup before upgrading! See our postgres 12 end of life notice!
Warning:
automaticand migratorupgradecommand will not work for this release, please upgrade directly tov5.10.1164, or to a 5.9 version and conduct a standard upgrade using migrator's defaultupcommand!
Notes:
- The container image for pgsql and codeintel-db have been renamed from
postgres-12-alpineandcodeintel-dbrespectively topostgresql-16. Thecodeinsights-dbcontainer has been renamed topostgresql-16-codeinsights. - Admins using external dbs who have not yet upgraded from postgres 12 to postgres 16, can expect to see database drift after upgrading to
5.10.0. The new expected schema definition for Sourcegraph is based on postgres 16. The schema drift is the result of automatic changes made to the schema by pg_upgrade utils, and will not cause issues in the application.- Admins should not run migrators suggested drift fixes, and should instead upgrade their database from postgres 12 to postgres 16.
- For versions prior to 6.12.0, the Autoupgrade upgrade method would detect drift and exit before conducting the upgrade unless the env var
SRC_AUTOUPGRADE_IGNORE_DRIFT=truewas set in the server container. Note: Autoupgrade has been removed in Sourcegraph 6.12.0 and later. - Postgres 12 image containers cannot be started with data volumes which have been upgraded by postgres 16.
5.1.5
Notes:
- Upgrades from versions
v5.0.3,v5.0.4,v5.0.5, andv5.0.6tov5.1.5are affected by an ordering error in thefrontenddatabases migration tree.
5.1.4
Notes:
- Migrator images were built without the
v5.1.xtag in this version, as such multiversion upgrades using this image version will fail to upgrade to versions inv5.1.x.
5.1.3
Notes:
- Migrator images were built without the
v5.1.xtag in this version, as such multiversion upgrades using this image version will fail to upgrade to versions inv5.1.x.
5.1.2
Notes:
- Migrator images were built without the
v5.1.xtag in this version, as such multiversion upgrades using this image version will fail to upgrade to versions inv5.1.x.
5.1.1
Notes:
- Migrator images were built without the
v5.1.xtag in this version, as such multiversion upgrades using this image version will fail to upgrade to versions inv5.1.x.
5.1.0
Notes:
- See note under v5.1.5 release on issues with standard and multiversion upgrades to v5.1.5.
5.0.6
Notes:
- See note under v5.1.5 release on issues with standard and multiversion upgrades to v5.1.5.
5.0.5
Notes:
- See note under v5.1.5 release on issues with standard and multiversion upgrades to v5.1.5.
5.0.4
Notes:
- See note under v5.1.5 release on issues with standard and multiversion upgrades to v5.1.5.
To upgrade from older versions, please contact support.