This repository will provide you fully functional PHP-FPM 7.3 Docker images in different flavours and packed with different types of integrated PHP modules. It also solves the problem of syncronizing file permissions of mounted volumes between the host and the container.
Choose between Alpine or Debian and select an image type for extending, use in production or use for local development. Images are always guaranteed to be fresh and up-to-date as they are automatically built every night by travis-ci and pushed to Docker hub.
| Docker Hub | Upstream Project |
|---|---|
 |
 |
Select different version
PHP 5.4 | PHP 5.5 | PHP 5.6 | PHP 7.0 | PHP 7.1 | PHP 7.2 | PHP 7.3 | HHVM latest
- Motivation
- PHP-FPM 7.3 Flavours
- PHP-FPM 7.3 Features
- PHP-FPM 7.3 Options
- Integrated Development Environment
- Examples
- Automated builds
- Contributing
- Credits
- License
One main problem with a running Docker container is to synchronize the ownership of files in a mounted volume in order to preserve security (Not having to use chmod 0777).
Consider the following directory structure of a mounted volume. Your hosts computer uid/gid are 1000 which does not have a corresponding user/group within the container. Fortunately the tmp/ directory allows everybody to create new files in it.
[Host] | [Container]
------------------------------------------------------------------------------------------
$ ls -l | $ ls -l
-rw-r--r-- user group index.php | -rw-r--r-- 1000 1000 index.php
drwxrwxrwx user group tmp/ | drwxrwxrwx 1000 1000 tmp/Your web application might now have created some temporary files (via the PHP-FPM process) inside the tmp/ directory:
[Host] | [Container]
------------------------------------------------------------------------------------------
$ ls -l tmp/ | $ ls -l tmp/
-rw-r--r-- 96 96 _tmp_cache01.php | -rw-r--r-- www www _tmp_cache01.php
-rw-r--r-- 96 96 _tmp_cache02.php | -rw-r--r-- www www _tmp_cache01.phpOn the Docker container side everything is still fine, but on your host computers side, those files now show a user id and group id of 96, which is in fact the uid/gid of the PHP-FPM process running inside the container. On the host side you will now have to use sudo in order to delete/edit those files.
Consider your had created the tmp/ directory on your host only with 0775 permissions:
[Host] | [Container]
------------------------------------------------------------------------------------------
$ ls -l | $ ls -l
-rw-r--r-- user group index.php | -rw-r--r-- 1000 1000 index.php
drwxrwxr-x user group tmp/ | drwxrwxr-x 1000 1000 tmp/If your web application now wants to create some temporary files (via the PHP-FPM process) inside the tmp/ directory, it will fail due to lacking permissions.
To overcome this problem, it must be made sure that the PHP-FPM process inside the container runs under the same uid/gid as your local user that mouns the volumes and also wants to work on those files locally. However, you never know during Image build time what user id this would be. Therefore it must be something that can be changed during startup of the container.
This is achieved by two environment variables that can be provided during startup in order to change the uid/gid of the PHP-FPM user prior starting up PHP-FPM.
$ docker run -e NEW_UID=1000 -e NEW_GID=1000 -it devilbox/php-fpm-7.3:base-alpine
[INFO] Changing user 'devilbox' uid to: 1000
root $ usermod -u 1000 devilbox
[INFO] Changing group 'devilbox' gid to: 1000
root $ groupmod -g 1000 devilbox
[INFO] Starting PHP 7.3.0-dev (fpm-fcgi) (built: Oct 30 2017 12:05:19)When NEW_UID and NEW_GID are provided to the startup command, the container will do a usermod and groupmod prior starting up in order to assign new uid/gid to the PHP-FPM user. When the PHP-FPM process finally starts up it actually runs with your local system user and making sure permissions will be in sync from now on.
At a minimum those two environment variables are offered by all flavours and types of the here provided PHP-FPM images.
Note:
To tackle this on the PHP-FPM side is only half a solution to the problem. The same applies to a web server Docker container when you offer file uploads. They will be uploaded and created by the web servers uid/gid. Therefore the web server itself must also provide the same kind of solution. See the following Web server Docker images for how this is done:
Apache 2.2 | Apache 2.4 | Nginx stable | Nginx mainline
The provided Docker images heavily rely on inheritance to guarantee smallest possible image size. Each of them provide a working PHP-FPM server and you must decide what version works best for you. Look at the sketch below to get an overview about the two provided flavours and each of their different types.
[Alpine] [Debian] # Base FROM image
^ ^ #
| | #
| | #
[base-alpine] [base-debian] # Clones PHP git repository, compiles
^ ^ # and installs it
| | #
| | #
[mods-alpine] [mods-debian] # Installs additional PHP modules
^ ^ # via pecl
| | #
| | #
[prod-alpine] [prod-debian] # Devilbox flavour for production
^ ^ # (locales, postifx, socat and injectables)
| | # (custom modules and *.ini files)
| | #
[work-alpine] [work-debian] # Devilbox flavour for local development
# (includes backup and development tools)
# (sudo, custom bash and tool configs)The following table shows a more complete overview about the offered Docker images and what they should be used for.
| Type | Docker Image | Description |
|---|---|---|
| base | devilbox/php-fpm-7.3:base-alpine |
|
devilbox/php-fpm-7.3:base-debian |
|
|
| mods | devilbox/php-fpm-7.3:mods-alpine |
|
devilbox/php-fpm-7.3:mods-debian |
|
|
| prod | devilbox/php-fpm-7.3:prod-alpine |
|
devilbox/php-fpm-7.3:prod-debian |
|
|
| work | devilbox/php-fpm-7.3:work-alpine |
|
devilbox/php-fpm-7.3:work-debian |
|
|
This repository uses Docker tags to refer to different flavours and types of the PHP-FPM 7.3 Docker image. Therefore :latest and :<git-branch-name> as well as :<git-tag-name> must be presented differently. Refer to the following table to see how tagged Docker images are produced at Docker hub:
| Meant Tag | Actual Tag | Comment |
|---|---|---|
:latest |
:base-alpine:base-debian:mods-alpine:mods-debian:prod-alpine:prod-debian:work-alpine:work-debian
|
Stable (rolling) These tags are produced by the master branch of this repository. |
:<git-tag-name> |
:base-alpine-<git-tag-name>:base-debian-<git-tag-name>:mods-alpine-<git-tag-name>:mods-debian-<git-tag-name>:prod-alpine-<git-tag-name>:prod-debian-<git-tag-name>:work-alpine-<git-tag-name>:work-debian-<git-tag-name>
|
Stable (fixed) Every git tag will produce and preserve these Docker tags. |
:<git-branch-name> |
:base-alpine-<git-branch-name>:base-debian-<git-branch-name>:mods-alpine-<git-branch-name>:mods-debian-<git-branch-name>:prod-alpine-<git-branch-name>:prod-debian-<git-branch-name>:work-alpine-<git-branch-name>:work-debian-<git-branch-name>
|
Feature (for testing) Tags produced by unmerged branches. Do not rely on them as they might come and go. |
Check out this table to see which Docker image provides what PHP modules.
| Alpine | Debian | |
|---|---|---|
| base | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, interbase, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, PDO_Firebird, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib |
| mods | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imap, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imagick, imap, interbase, intl, json, ldap, libxml, mbstring, mongodb, msgpack, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, PDO_Firebird, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib |
| prod | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imap, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imagick, imap, interbase, intl, json, ldap, libxml, mbstring, mongodb, msgpack, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, PDO_Firebird, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib |
| work | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imap, intl, json, ldap, libxml, mbstring, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib | bcmath, bz2, calendar, Core, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, igbinary, imagick, imap, interbase, intl, json, ldap, libxml, mbstring, mongodb, msgpack, mysqli, mysqlnd, openssl, pcntl, pcre, PDO, PDO_Firebird, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, redis, Reflection, session, shmop, SimpleXML, snmp, soap, sockets, SPL, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, Zend OPcache, zip, zlib |
docker pull devilbox/php-fpm-7.3:base-alpine
docker pull devilbox/php-fpm-7.3:base-debianGeneric PHP-FPM base image. Use it to derive your own php-fpm docker image from it and add more extensions, tools and injectables.
(Does not offer any environment variables except for NEW_UID and NEW_GID)
docker pull devilbox/php-fpm-7.3:mods-alpine
docker pull devilbox/php-fpm-7.3:mods-debianGeneric PHP-FPM image with fully loaded extensions. Use it to derive your own php-fpm docker image from it and add more extensions, tools and injectables.
(Does not offer any environment variables except for NEW_UID and NEW_GID)
docker pull devilbox/php-fpm-7.3:prod-alpine
docker pull devilbox/php-fpm-7.3:prod-debianDevilbox production image. This Docker image comes with many injectables, port-forwardings, mail-catch-all and user/group rewriting.
docker pull devilbox/php-fpm-7.3:work-alpine
docker pull devilbox/php-fpm-7.3:work-debianDevilbox development image. Same as prod, but comes with lots of locally installed tools to make development inside the container as convenient as possible. See Integrated Development Environment for more information about this.
Have a look at the following table to see all supported environment variables for each Docker image flavour.
| Image | Env Variable | Type | Default | Description |
|---|---|---|---|---|
| base mods prod work |
DEBUG_ENTRYPOINT |
int | 0 |
Set debug level for startup.0 Only warnings and errors are shown.1 All log messages are shown2 All log messages and executed commands are shown. |
NEW_UID |
int | 1000 |
Assign the PHP-FPM user a new uid in order to syncronize file system permissions with your host computer and the Docker container. You should use a value that matches your host systems local user.(Type id for your uid). |
|
NEW_GID |
int | 1000 |
Assign the PHP-FPM group a new gid in order to syncronize file system permissions with your host computer and the Docker container. You should use a value that matches your host systems local group.(Type id for your gid). |
|
| prod work |
TIMEZONE |
string | UTC |
Set docker OS timezone as well as PHP timezone. (Example: Europe/Berlin) |
DOCKER_LOGS |
bool | 1 |
By default all Docker images are configured to output their PHP-FPM access and error logs to stdout and stderr. Those which support it can change the behaviour to log into files inside the container. Their respective directories are available as volumes that can be mounted to the host computer. This feature might help developer who are more comfortable with tailing or searching through actual files instead of using docker logs. Set this variable to 0 in order to enable logging to files. Log files are avilable under /var/log/php/ which is also a docker volume that can be mounted locally. |
|
ENABLE_MAIL |
bool | 0 |
Enable local email catch-all. Postfix will be configured for local delivery and all mails sent (even to real domains) will be catched locally. No email will ever go out. They will all be stored in a local devilbox account. Value: 0 or 1 |
|
FORWARD_PORTS_TO_LOCALHOST |
string | List of remote ports to forward to 127.0.0.1. Format: <local-port>:<remote-host>:<remote-port>You can separate multiple entries by comma. Example: 3306:mysqlhost:3306, 6379:192.0.1.1:6379 |
||
| work | MYSQL_BACKUP_USER |
string | '' |
Username for mysql backups used for bundled mysqldump-secure |
MYSQL_BACKUP_PASS |
string | '' |
Password for mysql backups used for bundled mysqldump-secure | |
MYSQL_BACKUP_HOST |
string | '' |
Hostname for mysql backups used for bundled mysqldump-secure | |
Have a look at the following table to see all offered volumes for each Docker image flavour.
| Image | Volumes | Description |
|---|---|---|
| prod work |
/etc/php-custom.d |
Mount this directory into your host computer and add custom \*.ini files in order to alter php behaviour. |
/etc/php-modules.d |
Mount this directory into your host computer and add custo \*.so files in order to add your php modules.Note:Your should then also provide a custom \*.ini file in order to actually load your custom provided module. |
|
/var/log/php |
When setting environment variable DOCKER_LOGS to 0, log files will be available under this directory. |
|
/var/mail |
Emails caught be the postfix catch-all (ENABLE_MAIL=1) will be available in this directory. |
|
| work | /etc/bash-custom.d |
Mount this directory into your host computer and add custom configuration files for bash and other tools. |
/shared/backups |
Mount this directory into your host computer to access MySQL backups created by mysqldump-secure. | |
Have a look at the following table to see all offered exposed ports for each Docker image flavour.
| Image | Port | Description |
|---|---|---|
| base mods prod work |
9000 |
PHP-FPM listening port |
If you plan to use the PHP-FPM image for development, hence being able to execute common commands inside the container itself, you should go with the work Image.
The work Docker image has many common tools already installed which on one hand increases its image size, but on the other hand removes the necessity to install those tools locally.
You want to use tools such as git, drush, composer, npm, eslint, phpcs as well as many others, simply do it directly inside the container. As all Docker images are auto-built every night by travis-ci it is assured that you are always at the latest version of your favorite dev tool.
| Tool | Description |
|---|---|
| awesome-ci | Various linting and source code analyzing tools. |
| composer | Dependency Manager for PHP. |
| drupal-console | The Drupal CLI. A tool to generate boilerplate code, interact with and debug Drupal. |
| drush | Drush is a computer software shell-based application used to control, manipulate, and administer Drupal websites. |
| eslint | The pluggable linting utility for JavaScript and JSX. |
| git | Git is a version control system for tracking changes in source files. |
| laravel installer | A CLI tool to easily install and manage the laravel framework. |
| linuxbrew | The Homebrew package manager for Linux. |
| mysqldump-secure | Secury MySQL database backup tool with encryption. |
| nodejs | Node.js is an open-source, cross-platform JavaScript run-time environment for executing JavaScript code server-side. |
| npm | npm is a package manager for the JavaScript programming language. |
| phalcon-devtools | CLI tool to generate code helping to develop faster and easy applications that use with Phalcon framework. |
| phpcs | PHP_CodeSniffer tokenizes PHP, JavaScript and CSS files and detects violations of a defined set of coding standards.. |
| symfony installer | This is the official installer to start new projects based on the Symfony full-stack framework. |
| webpack | A bundler for javascript and friends. |
| wp-cli | WP-CLI is the command-line interface for WordPress. |
Apart from the provided tools, you will also be able to use the container similar as you would do with your host system. Just a few things to mention here:
- Mount custom bash configuration files so your config persists between restarts
- Use password-less
sudoto become root and do whatever you need to do
If there is anything else you'd like to be able to do, drop me an issue.
$ docker run -d \
-p 127.0.0.1:9000:9000 \
-t devilbox/php-fpm-7.3:prod-debian$ docker run -d \
-p 127.0.0.1:9000:9000 \
-e TIMEZONE=Europe/Berlin \
-t devilbox/php-fpm-7.3:prod-debianconfig/ is a local directory that will hold the PHP *.ini files you want to load into the Docker container.
# Create config directory to be mounted with dummy configuration
$ mkdir config
$ echo "xdebug.enable = 1" > config/xdebug.ini
# Run container and mount it
$ docker run -d \
-p 127.0.0.1:9000:9000 \
-v config:/etc/php-custom.d \
-t devilbox/php-fpm-7.3:prod-debianmodules/ is a local directory that will hold the PHP modules you want to mount into the Docker container. config/ is a local directory that will hold the PHP *.ini files you want to load into the Docker container.
# Create module directory and place module into it
$ mkdir modules
$ cp /my/module/phalcon.so modules/
# Custom php config to load this module
$ mkdir config
$ echo "extension=/etc/php-modules.d/phalcon.so" > config/phalcon.ini
# Run container and mount it
$ docker run -d \
-p 127.0.0.1:9000:9000 \
-v config:/etc/php-custom.d \
-v modules:/etc/php-modules.d \
-t devilbox/php-fpm-7.3:prod-debianForward MySQL Port from 172.168.0.30 (or any other IP address/hostname) and Port 3306 to the PHP docker on 127.0.0.1:3306. By this, your PHP files inside the docker can use 127.0.0.1 to connect to a MySQL database.
$ docker run -d \
-p 127.0.0.1:9000:9000 \
-e FORWARD_PORTS_TO_LOCALHOST='3306:172.168.0.30:3306' \
-t devilbox/php-fpm-7.3:prod-debianForward MySQL Port from 172.168.0.30:3306 and Redis port from redis:6379 to the PHP docker on 127.0.0.1:3306 and 127.0.0.1:6379. By this, your PHP files inside the docker can use 127.0.0.1 to connect to a MySQL or Redis database.
$ docker run -d \
-p 127.0.0.1:9000:9000 \
-e FORWARD_PORTS_TO_LOCALHOST='3306:172.168.0.30:3306, 6379:redis:6379' \
-t devilbox/php-fpm-7.3:prod-debianOnce you set $ENABLE_MAIL=1, all mails sent via any of your PHP applications no matter to which domain, are catched locally into the devilbox account. You can also mount the mail directory locally to hook in with mutt and read those mails.
$ docker run -d \
-p 127.0.0.1:9000:9000 \
-v /tmp/mail:/var/mail \
-e ENABLE_MAIL=1 \
-t devilbox/php-fpm-7.3:prod-debian~/my-host-www will be the directory that serves the php files (your document root). Make sure to mount it into both, php and the webserver.
# Start PHP-FPM container
$ docker run -d \
-v ~/my-host-www:/var/www/default/htdocs \
--name php \
-t devilbox/php-fpm-7.3:prod-debian
# Start webserver and link with PHP-FPM
$ docker run -d \
-p 80:80 \
-v ~/my-host-www:/var/www/default/htdocs \
-e PHP_FPM_ENABLE=1 \
-e PHP_FPM_SERVER_ADDR=php \
-e PHP_FPM_SERVER_PORT=9000 \
--link php \
-t devilbox/nginx-mainlineNote: This will only work with work-(alpine|debian) Docker images.
The MySQL server could be another Docker container linked to the PHP-FPM container. Let's assume the PHP-FPM container is able to access the MySQL container by the hostname mysql.
# Start container
$ docker run -d \
-e MYSQL_BACKUP_USER=root \
-e MYSQL_BACKUP_PASS=somepass \
-e MYSQL_BACKUP_HOST=mysql \
-v ~/backups:/shared/backsup \
--name php \
-t devilbox/php-fpm-7.3:work-debian
# Run database dump
$ docker exec -it php mysqldump-secure
Docker images are built and tested every night by travis-ci and pushed to Docker hub on success. This is all done automatically to ensure that sources as well as base images are always fresh and in case of security updates always have the latest patches.
Contributors are welcome. Feel free to star and clone this repository and submit issues and pull-requests. Add examples and show what you have created with the provided images. If you see any errors or ways to improve this repository in any way, please do so.
Copyright (c) 2017 cytopia