Detailed tutorial on installing php-fpm service/extension/configuration in docker

When I installed php56 with brew on mac , I encountered various errors that even google couldn't figure out because openssl was version 1.1 It was too much trouble. Now I use docker to create a php56-fpm service container and install nginx directly on the host machine.

PHP DockerHub Home Page

Create a container

# Create a container docker run -d \
--name php56-fpm \
-p 9056:9000 \
-v /home/wwwroot:/var/www/html
--privileged=true
php:5.6-fpm

Notice:

/var/www/html is the working directory of php docker image.

-v /home/wwwroot:/var/www/html is used to mount the host's site directory to the container. For example, /home/wwwroot/siteA is accessible in the container as /var/www/html/siteA .

When nignx forwards php request, it forwards the executed script name SCRIPT_NAME and the script file name SCRIPT_FILENAME to fpm , and then fpm reads the script for execution.

When using the fpm container, you need to pay attention to whether SCRIPT_FILENAME forwarded by nginx is a valid site path in the fpm container. If root of nginx cannot be directly mapped to the site root of the fpm container, we need to redefine it in php location as the site root of fpm container. In this way, fpm can read the script correctly.

That is, /home/wwwroot/siteA/public/index.php on the host machine must be converted to /var/www/html/siteA/public/index.php and sent to fpm container, otherwise an error of File not found will be reported.

Therefore, when configuring nginx server , pay attention to the following volume path conversion:

server {
 listen 8056;
 ....
 # The host's site root directory root /home/wwwroot/siteA/public;
 
 location ~* (^[/]*.php)[/|$] {
 # Site root directory in the container /var/www/html/siteA/public;
 pass_proxy: 127.0.0.1:9056;
 include fastcgi.conf;
 }
}

However, in general, everyone uses docker nginx + docker php-fpm , and both containers map the site directory uniformly, so there will be no such problem. nginx here is installed directly on the host machine, which causes the root directory of the site to need to be redefined when nginx forwards php requests.

Login container

# Check if the container is running docker ps

# Log in to the container docker exec -it php56-fpm /bin/bash

The docker image of php is based on ubuntu. We can use apt-get to install the required tools, such as vim/vi lrzsz net-tools and so on.

# Before using apt-get to install some tools, you need to update the source # Otherwise, apt-get E: Unable to locate package
apt-get update
apt-get install vim

Install php/pecl extension

Install PHP extension

That is, the official PHP extension, such as shomp, which comes with it but is not enabled by default.

# Check the built-in extensions cd /usr/local/php/ext && ls -l
# Install the extension dcoker-php-ext-install shmop

Install pecl extension

Pecl is installed in the container, so you can directly use pecl to install it. Pay attention to extending the support for PHP version.

The main purpose of docker-php-ext-enable is to generate the corresponding configuration file for the extension to /usr/local/etc/php/conf.d/docker-php-ext-{extName}.ini to facilitate PHP to load the extension.

# igbinary php5.6 highest version is 2.0.8
pecl install igbinary-2.0.8
docker-php-ext-enable igbinary

# The highest version of phpredis php5.6 is 4.3.0
pecl install redis-4.3.0
docker-php-ext-enable redis

# The highest version of swoole php5.6 is 2.0.11
pcel install swoole-2.0.11
docker-php-ext-enable swoole

php/php-fpm configuration

/usr/local/etc is the configuration directory of the PHP container, which contains the configuration files of PHP and PHP-FPM. The configuration directory structure is as follows:

root@aa739592b579:/usr/local# tree etc/ 
etc/
|-- pear.conf
|-- php # php configuration directory| |-- conf.d # php extended configuration| | |-- docker-php-ext-shmop.ini
| |-- php.ini # cp of php.ini-development/production
| |-- php.ini-development
| |-- php.ini-production
|-- php-fpm.conf # The configuration of php-fpm mainly introduces php-fpm.d
|-- php-fpm.conf.default # The php-fpm configuration is the same as php-fpm.d/www.conf |-- php-fpm.d # Extended configuration of php-fpm |-- docker.conf
 |-- www.conf # php-fpm configuration mode max/min children are all here |-- zz-docker.conf

You can map the host's configuration directory to the container's /usr/local/etc, but be careful to keep the configuration directory on the host consistent with the existing one in the container, or edit the configuration file directly in the container. According to the Docker concept, we should maintain a configuration file on the host machine and map it to the container's configuration directory, so as to give full play to the reusability of the Docker container.

Map the host's PHP configuration file to the container

-v /opt/docker/conf/php/php.ini:/usr/local/etc/php/php.ini
-v /opt/docker/conf/php/php-fpm.ini:/usr/local/etc/php-fpm.d/www/conf

Frequently asked questions

1. File not found
The site root directory specified by nginx cannot be directly mapped to the fpm container. Re-specify the site root directory of the fpm container in location.

2. apt-get E: Unable to locate package
Run apt-get update to refresh the source.

3. Container-related conventions Working directory: /var/www/html It is recommended to map the host's site directory to this directory Configuration directory: /usr/local/etc Pay attention to the configuration directory structure
PHP extension directory: /usr/local/php/ext You can view the built-in extension package of PHP. It is more convenient to install it using docker-php-ext-install

This is the end of this article about installing php-fpm service/extension/configuration with docker. For more information about installing php-fpm with docker, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope you will support 123WORDPRESS.COM in the future!