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

php-fpm.org

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

phpfpm:
  image: bitnami/php-fpm
  volumes:
    - /path/to/app:/app

The recommended way to get the Bitnami PHP-FPM Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/php-fpm:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/php-fpm:[TAG]

If you wish, you can also build the image yourself.

docker build -t bitnami/php-fpm https://github.com/bitnami/bitnami-docker-php-fpm.git

This image is designed to be used with a web server to serve your PHP app, you can use the linking system provided by Docker to do this.

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.

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

server {
    listen 0.0.0.0:80;
    server_name yourapp.com;

    root /app;

    location / {
        index index.php;
    }

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

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

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

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 run -it --name phpfpm -v /path/to/app:/app bitnami/php-fpm

or using Docker Compose:

phpfpm:
  image: bitnami/php-fpm
  volumes:
    - /path/to/app:/app

Now that we have our PHP-FPM server running, we can create another container that links to it by giving Docker the --link option. This option takes the id or name of the container we want to link it to as well as a hostname to use inside the container, separated by a colon. For example, to have our PHP-FPM server accessible in another container with yourapp as it's hostname we would pass --link phpfpm:yourapp to the Docker run command.

docker run -it -v /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf \
  --link phpfpm:yourapp \
  bitnami/nginx

or using Docker Compose:

nginx:
  image: bitnami/nginx
  links:
    - phpfpm:yourapp
  volumes:
    - /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf

We started the nginx server, mounting the virtual host we created in Step 1, and created a link to the PHP-FPM server with the alias yourapp.

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.

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

docker run -it --name phpfpm bitnami/php-fpm php -a

Further Reading:

• PHP Interactive Shell Documentation

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 bitnami/php-fpm \
  php script.php

This container looks for configurations in /bitnami/php-fpm/conf. You can mount a directory at /bitnami/php-fpm with your own configurations in conf/, or the default configuration will be copied at conf/ if it is empty.

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

docker run --name phpfpm -v /path/to/php-fpm:/bitnami/php-fpm bitnami/php-fpm

or using Docker Compose:

phpfpm:
  image: bitnami/php-fpm
  volumes:
    - /path/to/php-fpm:/bitnami/php-fpm

Edit the configuration on your host using your favorite editor.

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

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

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.

To backup your configurations, follow these simple steps:

docker stop phpfpm

or using Docker Compose:

docker-compose stop phpfpm

We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.

docker run --rm -v /path/to/backups:/backups --volumes-from phpfpm busybox \
  cp -a /bitnami/php-fpm /backups/latest

or using Docker Compose:

docker run --rm -v /path/to/backups:/backups --volumes-from `docker-compose ps -q phpfpm` busybox \
  cp -a /bitnami/php-fpm /backups/latest

Restoring a backup is as simple as mounting the backup as volumes in the container.

docker run -v /path/to/backups/latest:/bitnami/php-fpm \
  bitnami/php-fpm

or using Docker Compose:

phpfpm:
  image: bitnami/php-fpm
  volumes:
    - /path/to/backups/latest:/bitnami/php-fpm

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.

docker pull bitnami/php-fpm:latest

or if you're using Docker Compose, update the value of the image property to bitnami/php-fpm:latest.

Before continuing, you should backup your container's configuration and logs.

Follow the steps on creating a backup.

docker rm -v phpfpm

or using Docker Compose:

docker-compose rm -v phpfpm

Re-create your container from the new image, restoring your backup if necessary.

docker run --name phpfpm bitnami/php-fpm:latest

or using Docker Compose:

docker-compose start phpfpm

This image is tested for expected runtime behavior, using the Bats testing framework. You can run the tests on your machine using the bats command.

bats test.sh

• 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.

• Enables support for imagick extension

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

• /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_APP_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright 2015 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

http://www.apache.org/licenses/LICENSE-2.0

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.