No description or website provided.
Switch branches/tags
Clone or download
Latest commit b20c6de May 3, 2018

What is PHP-FPM?

PHP-FPM (FastCGI Process Manager) is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites.


$ docker run -it --name phpfpm -v /path/to/app:/app bitnami/php-fpm-redhat

Docker Compose

$ curl -sSL > docker-compose.yml
$ docker-compose up -d

Why use Bitnami Images?

  • Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
  • With Bitnami images the latest bug fixes and features are available as soon as possible.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • Bitnami images are built on CircleCI and automatically pushed to the Docker Hub.

Supported tags and respective Dockerfile links

Subscribe to project updates by watching the bitnami/php-fpm GitHub repo.

Connecting to other containers

This image is designed to be used with a web server to serve your PHP app, you can use docker networking to create a network and attach all the containers to that network.

Serving your PHP app through an nginx frontend

We will use PHP-FPM with nginx to serve our PHP app. Doing so will allow us to setup more complex configuration, serve static assets using nginx, load balance to different PHP-FPM instances, etc.

Step 1: Create a network

$ docker network create app-tier --driver bridge

or using Docker Compose:

version: '2'

    driver: bridge

Step 2: Create a virtual host

Let's create an nginx virtual host to reverse proxy to our PHP-FPM container.

server {

  root /app;

  location / {
    try_files $uri $uri/index.php;

  location ~ \.php$ {
    # fastcgi_pass [PHP_FPM_LINK_NAME]:9000;
    fastcgi_pass phpfpm:9000;
    fastcgi_index index.php;
    include fastcgi.conf;

Notice we've substituted the link alias name myapp, we will use the same name when creating the container.

Copy the virtual host above, saving the file somewhere on your host. We will mount it as a volume in our nginx container.

Step 3: Run the PHP-FPM image with a specific name

Docker's linking system uses container ids or names to reference containers. We can explicitly specify a name for our PHP-FPM server to make it easier to connect to other containers.

$ docker build -t php-fpm-redhat .
$ docker run -it --name phpfpm \
  --network app-tier
  -v /path/to/app:/app \

or using Docker Compose:

      context: ./7.2
      dockerfile: Dockerfile
      - app-tier
      - /path/to/app:/app

Step 4: Run the nginx image

$ docker run -it \
  -v /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf \
  --network app-tier \

or using Docker Compose:

    image: 'bitnami/nginx:latest'
      - phpfpm
      - app-tier
      - '80:80'
      - '443:443'
      - /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf

PHP runtime

Since this image bundles a PHP runtime, you may want to make use of PHP outside of PHP-FPM. By default, running this image will start a server. To use the PHP runtime instead, we can override the the default command Docker runs by stating a different command to run after the image name.

Entering the REPL

PHP provides a REPL where you can interactively test and try things out in PHP.

$ docker run -it --name phpfpm php-fpm-redhat php -a

Further Reading:

Running your PHP script

The default work directory for the PHP-FPM image is /app. You can mount a folder from your host here that includes your PHP script, and run it normally using the php command.

$ docker run -it --name php-fpm -v /path/to/app:/app php-fpm-redhat \
  php script.php


Mount a custom config file

You can mount a custom config file from your host to edit the default configuration for the php-fpm docker image. The following is an example to alter the configuration of the php-fpm.conf configuration file:

Step 1: Run the PHP-FPM image

Run the PHP-FPM image, mounting a file from your host.

$ docker run --name phpfpm -v /path/to/php-fpm.conf:/opt/bitnami/php/etc/php-fpm.conf php-fpm-redhat

or using Docker Compose:

version: '2'

      context: ./7.2
      dockerfile: Dockerfile
      - '9000:9000'
      - /path/to/php-fpm.conf:/opt/bitnami/php/etc/php-fpm.conf

Step 2: Edit the configuration

Edit the configuration on your host using your favorite editor.

$ vi /path/to/php-fpm.conf

Step 3: Restart PHP-FPM

After changing the configuration, restart your PHP-FPM container for the changes to take effect.

$ docker restart phpfpm

or using Docker Compose:

$ docker-compose restart phpfpm

Add additional .ini files

PHP has been configured at compile time to scan the /opt/bitnami/php/etc/conf.d/ folder for extra .ini configuration files so it is also possible to mount your customizations there.

Multiple files are loaded in alphabetical order. It is common to have a file per extension and use a numeric prefix to guarantee an order loading the configuration.

Please check to know more about this feature.

In order to override the default max_file_uploads settings you can do the following:

  1. Create a file called custom.ini with the following content:
max_file_uploads = 30M
  1. Run the php-fpm container mounting the custom file.
$ docker run -it -v /path/to/custom.ini:/opt/bitnami/php/etc/conf.d/custom.ini php-fpm-redhat php -i | grep max_file_uploads

You should see that PHP is using the new specified value for the max_file_uploads setting.


The Bitnami PHP-FPM Docker Image sends the container logs to the stdout. You can configure the containers logging driver using the --log-driver option. By defauly the json-file driver is used.

To view the logs:

$ docker logs phpfpm

or using Docker Compose:

$ docker-compose logs phpfpm

The docker logs command is only available when the json-file or journald logging driver is in use.


Upgrade this image

Bitnami provides up-to-date versions of PHP-FPM, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.

Step 1: Get the updated image

$ git pull
$ docker build -t php-fpm-redhat .

or if you're using Docker Compose, just git pull

Step 2: Stop and backup the currently running container

Stop the currently running container using the command

$ docker stop phpfpm

or using Docker Compose:

$ docker-compose stop phpfpm

Next, take a snapshot of the persistent volume /path/to/php-fpm-persistence using:

$ rsync -a /path/to/php-fpm-persistence /path/to/php-fpm-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

You can use this snapshot to restore the database state should the upgrade fail.

Step 3: Remove the currently running container

$ docker rm -v phpfpm

or using Docker Compose:

$ docker-compose rm -v phpfpm

Step 4: Run the new image

Re-create your container from the new image.

$ docker run --name phpfpm php-fpm-redhat

or using Docker Compose:

$ docker-compose start phpfpm

Useful Links

Notable Changes

7.2.3-r2, 7.1.15-r2, 7.0.28-r2 and 5.6.34-r2 (2018-03-13)

  • PHP has been configured at compile time to scan the /opt/bitnami/php/etc/conf.d/ folder for extra .ini configuration files.

7.0.6-r0 (2016-05-17)

  • All volumes have been merged at /bitnami/php-fpm. Now you only need to mount a single volume at /bitnami/php-fpm for persistence.
  • The logs are always sent to the stdout and are no longer collected in the volume.

5.5.30-2 (2015-12-07)

  • Enables support for imagick extension

5.5.30-0-r01 (2015-11-10)

  • php.ini is now exposed in the volume mounted at /bitnami/php-fpm/conf/ allowing users to change the defaults as per their requirements.

5.5.30-0 (2015-10-06)

  • /app directory is no longer exported as a volume. This caused problems when building on top of the image, since changes in the volume are not persisted between Dockerfile RUN instructions. To keep the previous behavior (so that you can mount the volume in another container), create the container with the -v /app option.


We'd love for you to contribute to this Docker image. You can request new features by creating an issue, or submit a pull request with your contribution.


If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

  • Host OS and version
  • Docker version (docker version)
  • Output of docker info
  • Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
  • The command you used to run the container, and any relevant output you saw (masking any sensitive information)


Copyright (c) 2015-2018 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.