From 610bab1146af8350263d3c29120406e0992d966a Mon Sep 17 00:00:00 2001 From: Ben Schumacher Date: Tue, 27 Jan 2026 15:36:00 +0100 Subject: [PATCH] Document migration from pids_limit to mem_limit for Docker deployments Add note explaining why pids_limit was removed in favor of mem_limit. PostgreSQL's one-process-per-connection model caused production failures with pids_limit: 100, restricting deployments to ~90-95 concurrent connections. Co-Authored-By: Claude Sonnet 4.5 --- source/deployment-guide/server/containers/install-docker.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/deployment-guide/server/containers/install-docker.rst b/source/deployment-guide/server/containers/install-docker.rst index ab7e5e105b3..5a34687849e 100644 --- a/source/deployment-guide/server/containers/install-docker.rst +++ b/source/deployment-guide/server/containers/install-docker.rst @@ -28,6 +28,10 @@ This section provides a quick start guide for deploying Mattermost on Docker by - The deployment configuration results in two separate containers: a container for the database and a container for the application. An optional third container results when using NGINX for reverse proxy. - Encountering issues with your Docker deployment? See the :doc:`Docker deployment troubleshooting ` documentation for details. +.. note:: + + **Resource limits:** Previous versions of the Docker deployment used ``pids_limit`` to constrain container processes. This caused PostgreSQL connection failures in production because PostgreSQL creates one process per connection, limiting deployments to ~90-95 concurrent connections with ``pids_limit: 100``. We now recommend using ``mem_limit`` instead to constrain resources while allowing normal connection scaling. See the `Mattermost Scaling for Enterprise documentation `__ for sizing guidance. + 1. In a terminal window, clone the repository and enter the directory. .. code-block:: sh