如何修改WordPress Docker容器的最大并发客户端数

Hey there! Let's walk through how to tweak the maximum number of concurrent clients that can connect to your WordPress Docker instance using the MaxClients directive—just a heads up, this is specific to Apache since most official WordPress Docker images use Apache under the hood. Also, note that in Apache 2.4+, MaxClients has been renamed to MaxRequestWorkers, but the functionality is identical.

方法一：修改Apache配置文件（持久化修改） #

If you want a permanent change that sticks even when you rebuild your container, here's what to do:

• First, locate the relevant Apache config file. In the official WordPress image, this is usually /etc/apache2/mods-available/mpm_prefork.conf (since MaxRequestWorkers belongs to the prefork MPM module).
• Steps to modify it directly in a running container:
  1. SSH into your running container:

     docker exec -it <your-wordpress-container-name> /bin/bash
     

  2. Edit the config file with a text editor like nano:

     nano /etc/apache2/mods-available/mpm_prefork.conf
     

  3. Look for the block below and adjust the MaxRequestWorkers value to your desired number:

     <IfModule mpm_prefork_module>
         StartServers             5
         MinSpareServers          5
         MaxSpareServers         10
         MaxRequestWorkers      150  # Replace this number with your target
         MaxConnectionsPerChild   0
     </IfModule>
     

  4. Save the file (Ctrl+O, then Enter in nano) and exit (Ctrl+X), then restart Apache to apply changes:

     service apache2 restart
     

• For a truly persistent setup, create a custom Dockerfile to build your own WordPress image with the modified config:

  FROM wordpress:latest
  # Copy your local modified mpm_prefork.conf into the image
  COPY ./mpm_prefork.conf /etc/apache2/mods-available/mpm_prefork.conf
  

  Then build your custom image:

  docker build -t my-custom-wordpress .
  

方法二：通过环境变量启动（动态调整） #

The official WordPress image doesn't have a built-in environment variable for this setting, but you can work around it with these two approaches:

方式A：启动时挂载本地配置文件 #

先在本地修改好mpm_prefork.conf，然后启动容器时将该文件挂载到容器内：

docker run -d \
  -p 80:80 \
  # 替换为你本地配置文件的实际路径
  -v /path/to/your/local/mpm_prefork.conf:/etc/apache2/mods-available/mpm_prefork.conf \
  wordpress:latest

方式B：用环境变量动态修改配置 #

你可以借助sed命令，在容器启动时动态替换配置文件中的默认值：

docker run -d \
  -p 80:80 \
  # 在这里设置你想要的最大连接数
  -e MAX_REQUEST_WORKERS=200 \
  wordpress:latest \
  bash -c "sed -i 's/MaxRequestWorkers      150/MaxRequestWorkers      $MAX_REQUEST_WORKERS/' /etc/apache2/mods-available/mpm_prefork.conf && apache2-foreground"

这个命令会先用环境变量的值更新配置文件，再正常启动Apache服务。

关键注意事项 #

• 如果你使用的是搭配Nginx的WordPress FPM镜像（而非默认的Apache镜像），MaxRequestWorkers/MaxClients就不适用了。你需要调整Nginx的worker_connections和PHP-FPM的pm.max_children等参数。
• 不要盲目设置过高的数值！每个Apache进程通常会占用20-50MB内存，要根据服务器的可用内存计算合适的数值，避免出现内存耗尽的问题。

内容的提问来源于stack exchange，提问作者Brandon