bitnami/php-fpm Docker 镜像 - 轩辕镜像

Bitnami Secure Image for PHP-FPM

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.

Overview of PHP-FPM Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.

TL;DR

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

Why use Bitnami Secure Images?

Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise OS Photon Linux. Why choose BSI images?

• Hardened secure images of popular open source software with Near-Zero Vulnerabilities
• Vulnerability Triage & Prioritization with VEX Statements, KEV and EPSS Scores
• Compliance focus with FIPS, STIG, and air-gap options, including secure bill of materials (SBOM)
• Software supply chain provenance attestation through in-toto
• First class support for the internet’s favorite Helm charts

Each image comes with valuable security metadata. You can view the metadata in our public catalog here. Note: Some data is only available with commercial subscriptions to BSI.

!Alt text !Alt text

If you are looking for our previous generation of images based on Debian Linux, please see the Bitnami Legacy registry.

Choosing between the Standard and Minimal image

This asset is available in two flavors: Standard and Minimal; designed to address different use cases and operational needs.

Standard images

The standard images are full-featured, production-ready containers built on top of secure base operating systems. They include:

• The complete runtime and commonly used system tools.
• A familiar Linux environment (shell, package manager, debugging utilities).
• Full compatibility with most CI/CD pipelines and existing workloads.

Recommended for:

• Development and testing environments.
• Workloads requiring package installation or debugging tools.
• Applications that depend on system utilities or shared libraries.

Minimal images

The minimal images are optimized, distroless-style containers derived from a stripped-down base. They only ship what’s strictly necessary to run the application; no shell, package manager, or extra libraries. They provide:

• Smaller size: Faster pull and startup times.
• Reduced *** surface: Fewer components and potential vulnerabilities.
• Simpler maintenance: Fewer dependencies to patch or update.

Recommended for:

• Production environments prioritizing performance and security.
• Regulated or security-sensitive workloads
• Containers built via multi-stage builds (e.g., Golang static binaries).

Supported tags and respective Dockerfile links

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

You can see the equivalence between the different tags by taking a look at the tags-info.yaml file present in the branch folder, i.e bitnami/ASSET/BRANCH/DISTRO/tags-info.yaml.

Subscribe to project updates by watching the bitnami/containers GitHub repo.

Deprecation Note (2022-01-21)

The prod tags has been removed; from now on just the regular container images will be released.

Deprecation Note (2020-08-18)

The formatting convention for prod tags has been changed:

• BRANCH-debian-10-prod is now tagged as BRANCH-prod-debian-10
• VERSION-debian-10-rX-prod is now tagged as VERSION-prod-debian-10-rX
• latest-prod is now deprecated

Get this image

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

console
docker pull REGISTRY_NAME/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.

console
docker pull REGISTRY_NAME/bitnami/php-fpm:[TAG]

If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the docker build command. Remember to replace the APP, VERSION and OPERATING-SYSTEM path placeholders in the example command below with the correct values.

console
git clone [***]
cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t REGISTRY_NAME/bitnami/APP:latest .

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

console
docker network create app-tier --driver bridge

or using Docker Compose:

yaml
version: '2'

networks:
  app-tier:
    driver: bridge

Step 2: Create a server block

Let's create an nginx server block to reverse proxy to our PHP-FPM container.

nginx
server {
  listen 0.0.0.0:80;
  server_name myapp.com;

  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 server block 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.

console
docker run -it --name phpfpm \
  --network app-tier
  -v /path/to/app:/app \
  bitnami/php-fpm

or using Docker Compose:

yaml
services:
  phpfpm:
    image: REGISTRY_NAME/bitnami/php-fpm:latest
    networks:
      - app-tier
    volumes:
      - /path/to/app:/app

Step 4: Run the nginx image

console
docker run -it \
  -v /path/to/server_block.conf:/opt/bitnami/nginx/conf/server_blocks/yourapp.conf \
  --network app-tier \
  bitnami/nginx

or using Docker Compose:

yaml
services:
  nginx:
    image: REGISTRY_NAME/bitnami/nginx:latest
    depends_on:
      - phpfpm
    networks:
      - app-tier
    ports:
      - 80:80
      - 443:443
    volumes:
      - /path/to/server_block.conf:/opt/bitnami/nginx/conf/server_blocks/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.

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

Further Reading:

• PHP Interactive Shell Documentation

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.

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

Configuration

Environment variables

Customizable environment variables

Read-only environment variables

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.

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

or by modifying the docker-compose.yml file present in this repository:

yaml
services:
  phpfpm:
  ...
    volumes:
      - /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.

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

console
docker restart phpfpm

or using Docker Compose:

console
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:

   config
   max_file_uploads = 30M
   

2. Run the php-fpm container mounting the custom file.

   console
   docker run -it -v /path/to/custom.ini:/opt/bitnami/php/etc/conf.d/custom.ini bitnami/php-fpm php -i | grep max_file_uploads
   
   

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

FIPS configuration in Bitnami Secure Images

The Bitnami PHP-FPM Docker image from the Bitnami Secure Images catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:

• OPENSSL_FIPS: whether OpenSSL runs in FIPS mode or not. yes (default), no.

Logging

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:

console
docker logs phpfpm

or using Docker Compose:

console
docker-compose logs phpfpm

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

Maintenance

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

console
docker pull REGISTRY_NAME/bitnami/php-fpm:latest

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

Step 2: Stop and backup the currently running container

Stop the currently running container using the command

console
docker stop php-fpm

or using Docker Compose:

console
docker-compose stop php-fpm

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

console
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

console
docker rm -v phpfpm

or using Docker Compose:

console
docker-compose rm -v phpfpm

Step 4: Run the new image

Re-create your container from the new image.

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

or using Docker Compose:

console
docker-compose up phpfpm

Useful Links

• Create An AMP Development Environment With Bitnami Containers
• Create An EMP Development Environment With Bitnami Containers

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.

Using docker-compose.yaml

Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes.

If you detect any issue in the docker-compose.yaml file, feel free to report it or contribute with a fix by following our Contributing Guidelines.

Contributing

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

Issues

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to fill the issue template.

License

Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.

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.