fix: pin postgres image to bookworm in docker_example (#13027)

* fix: pin postgres image to bookworm in docker_example to prevent collation mismatch

The postgres:16 tag silently moved its base from Debian Bookworm
(glibc 2.36) to Trixie (glibc 2.41), causing a recurring collation
version mismatch warning on existing langflow-postgres volumes.

Pin to postgres:16-bookworm in both docker-compose files and update
the README so existing data volumes keep matching the OS locale data.

Refs: #9608

* docs: pin postgres image to bookworm in current docs compose snippets

Mirror the docker_example pin in the four current docs that publish
copyable Compose snippets pairing postgres:16 with a persistent
langflow-postgres volume. Prevents the same Bookworm-to-Trixie
collation version mismatch warning when users follow docs instead
of docker_example.

Versioned historical docs are left as-is.

Refs: #9608

* fix: switch postgres pin from bookworm to trixie for OS consistency

Aligns the pinned postgres base with the langflow runtime image, which
moved to Debian Trixie in #12990. Keeping postgres on bookworm would
have diverged the stack and locked the database to an aging glibc that
will receive fewer security backports as bookworm ages into oldstable.

The pin itself still solves the original bug — postgres:16 cannot
silently roll its OS underneath an existing volume.

Document the one-time REFRESH COLLATION VERSION step for users
upgrading from a bookworm-initialized volume in docker_example/README.md.

Refs: #9608

Author: erichare

.secrets.baseline

@@ -237,7 +237,7 @@
         "filename": "docker_example/docker-compose.yml",
         "hashed_secret": "e80c4f90316c87b6b24d03890493c8d1c7c1c99d",
         "is_verified": false,
-        "line_number": 20,
+        "line_number": 24,
         "is_secret": false
       }
     ],
@@ -247,7 +247,7 @@
         "filename": "docker_example/pre.docker-compose.yml",
         "hashed_secret": "e80c4f90316c87b6b24d03890493c8d1c7c1c99d",
         "is_verified": false,
-        "line_number": 21,
+        "line_number": 25,
         "is_secret": false
       }
     ],
@@ -8253,5 +8253,5 @@
       }
     ]
   },
-  "generated_at": "2026-05-05T19:37:49Z"
+  "generated_at": "2026-05-07T19:13:33Z"
 }

docker_example/README.md

@@ -48,7 +48,7 @@ Volumes:
 
 ### PostgreSQL Service
 
-The `postgres` service uses the `postgres:16` Docker image and exposes port 5432.
+The `postgres` service uses the `postgres:16-trixie` Docker image and exposes port 5432. The image is pinned to a specific Debian base (`trixie`, Debian 13) so the `postgres:16` tag cannot silently roll its underlying OS, which would otherwise produce a glibc collation version mismatch warning on existing data volumes.
 
 Environment variables:
 
@@ -60,6 +60,26 @@ Volumes:
 
 - `langflow-postgres`: This volume is mapped to `/var/lib/postgresql/data` in the container.
 
+### Upgrading from a `bookworm`-initialized volume
+
+Earlier versions of this example used `postgres:16`, which initially shipped on Debian Bookworm (glibc 2.36). The pinned image now uses Trixie (glibc 2.41). On the first start against a volume that was initialized under Bookworm, PostgreSQL logs a one-time warning:
+
+```
+WARNING: database "langflow" has a collation version mismatch
+DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
+```
+
+To clear it, refresh the collation version against the running database (one-off, takes seconds on a typical Langflow database):
+
+```sh
+docker compose exec postgres \
+  psql -U langflow -d langflow \
+  -c "REINDEX DATABASE langflow;" \
+  -c "ALTER DATABASE langflow REFRESH COLLATION VERSION;"
+```
+
+Fresh installs are unaffected.
+
 ## Switching to a Specific LangFlow Version
 
 If you want to use a specific version of LangFlow, you can modify the `image` field under the `langflow` service in the Docker Compose file. For example, to use version 1.0-alpha, change `langflowai/langflow:latest` to `langflowai/langflow:1.0-alpha`.

docker_example/docker-compose.yml

@@ -14,7 +14,11 @@ services:
       - langflow-data:/app/langflow
 
   postgres:
-    image: postgres:16
+    # Pinned to a specific Debian base (trixie) so the postgres:16 tag does not
+    # silently roll its OS underneath us — that roll causes a glibc collation
+    # version mismatch warning on existing volumes. Matches the langflow image
+    # base. See https://github.com/langflow-ai/langflow/issues/9608
+    image: postgres:16-trixie
     environment:
       POSTGRES_USER: langflow
       POSTGRES_PASSWORD: langflow

docker_example/pre.docker-compose.yml

@@ -15,7 +15,11 @@ services:
       - langflow-data:/app/langflow
 
   postgres:
-    image: postgres:16
+    # Pinned to a specific Debian base (trixie) so the postgres:16 tag does not
+    # silently roll its OS underneath us — that roll causes a glibc collation
+    # version mismatch warning on existing volumes. Matches the langflow image
+    # base. See https://github.com/langflow-ai/langflow/issues/9608
+    image: postgres:16-trixie
     environment:
       POSTGRES_USER: langflow
       POSTGRES_PASSWORD: langflow

docs/docs/Deployment/deployment-docker.mdx

@@ -232,7 +232,10 @@ For example, this Docker Compose file uses a bind mount for Langflow data (`./la
         volumes:
           - ./langflow-data:/app/langflow
       postgres:
-        image: postgres:16
+        # Pinned to a specific Debian base (trixie) so the postgres:16 tag does
+        # not silently roll its OS, which triggers a glibc collation mismatch
+        # warning on existing volumes. See https://github.com/langflow-ai/langflow/issues/9608
+        image: postgres:16-trixie
         volumes:
           - langflow-postgres:/var/lib/postgresql/data
 

docs/docs/Develop/configuration-custom-database.mdx

@@ -124,7 +124,10 @@ For example:
     ```yaml
     services:
       postgres:
-        image: postgres:16
+        # Pinned to a specific Debian base (trixie) so the postgres:16 tag does
+        # not silently roll its OS, which triggers a glibc collation mismatch
+        # warning on existing volumes. See https://github.com/langflow-ai/langflow/issues/9608
+        image: postgres:16-trixie
         environment:
           - POSTGRES_USER=${POSTGRES_USER}
           - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}

docs/docs/Develop/enterprise-database-guide.mdx

@@ -67,7 +67,10 @@ For more information, see [Configure an external PostgreSQL database](/configura
         environment:
           - LANGFLOW_DATABASE_URL=postgresql://langflow:langflow@postgres:5432/langflow
       postgres:
-        image: postgres:16
+        # Pinned to a specific Debian base (trixie) so the postgres:16 tag does
+        # not silently roll its OS, which triggers a glibc collation mismatch
+        # warning on existing volumes. See https://github.com/langflow-ai/langflow/issues/9608
+        image: postgres:16-trixie
         ports:
           - "5432:5432"
         environment:

docs/docs/Develop/integrations-langfuse.mdx

@@ -107,7 +107,10 @@ As an alternative to the previous setup, particularly for self-hosted Langfuse,
           - langflow-data:/app/langflow
 
       postgres:
-        image: postgres:16
+        # Pinned to a specific Debian base (trixie) so the postgres:16 tag does
+        # not silently roll its OS, which triggers a glibc collation mismatch
+        # warning on existing volumes. See https://github.com/langflow-ai/langflow/issues/9608
+        image: postgres:16-trixie
         environment:
           POSTGRES_USER: langflow
           POSTGRES_PASSWORD: langflow