7.0.8-cli
,7.0-cli
,7-cli
,cli
,7.0.8
,7.0
,7
,latest
(7.0/Dockerfile)7.0.8-alpine
,7.0-alpine
,7-alpine
,alpine
(7.0/alpine/Dockerfile)7.0.8-apache
,7.0-apache
,7-apache
,apache
(7.0/apache/Dockerfile)7.0.8-fpm
,7.0-fpm
,7-fpm
,fpm
(7.0/fpm/Dockerfile)7.0.8-fpm-alpine
,7.0-fpm-alpine
,7-fpm-alpine
,fpm-alpine
(7.0/fpm/alpine/Dockerfile)7.0.8-zts
,7.0-zts
,7-zts
,zts
(7.0/zts/Dockerfile)7.0.8-zts-alpine
,7.0-zts-alpine
,7-zts-alpine
,zts-alpine
(7.0/zts/alpine/Dockerfile)5.6.23-cli
,5.6-cli
,5-cli
,5.6.23
,5.6
,5
(5.6/Dockerfile)5.6.23-alpine
,5.6-alpine
,5-alpine
(5.6/alpine/Dockerfile)5.6.23-apache
,5.6-apache
,5-apache
(5.6/apache/Dockerfile)5.6.23-fpm
,5.6-fpm
,5-fpm
(5.6/fpm/Dockerfile)5.6.23-fpm-alpine
,5.6-fpm-alpine
,5-fpm-alpine
(5.6/fpm/alpine/Dockerfile)5.6.23-zts
,5.6-zts
,5-zts
(5.6/zts/Dockerfile)5.6.23-zts-alpine
,5.6-zts-alpine
,5-zts-alpine
(5.6/zts/alpine/Dockerfile)5.5.37-cli
,5.5-cli
,5.5.37
,5.5
(5.5/Dockerfile)5.5.37-alpine
,5.5-alpine
(5.5/alpine/Dockerfile)5.5.37-apache
,5.5-apache
(5.5/apache/Dockerfile)5.5.37-fpm
,5.5-fpm
(5.5/fpm/Dockerfile)5.5.37-fpm-alpine
,5.5-fpm-alpine
(5.5/fpm/alpine/Dockerfile)5.5.37-zts
,5.5-zts
(5.5/zts/Dockerfile)5.5.37-zts-alpine
,5.5-zts-alpine
(5.5/zts/alpine/Dockerfile)
For more information about this image and its history, please see the relevant manifest file (library/php
). This image is updated via pull requests to the docker-library/official-images
GitHub repo.
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the php/tag-details.md
file in the docker-library/docs
GitHub repo.
PHP is a server-side scripting language designed for web development, but which can also be used as a general-purpose programming language. PHP can be added to straight HTML or it can be used with a variety of templating engines and web frameworks. PHP code is usually processed by an interpreter, which is either implemented as a native module on the web-server or as a common gateway interface (CGI).
For PHP projects run through the command line interface (CLI), you can do the following.
FROM php:5.6-cli
COPY . /usr/src/myapp
WORKDIR /usr/src/myapp
CMD [ "php", "./your-script.php" ]
Then, run the commands to build and run the Docker image:
$ docker build -t my-php-app .
$ docker run -it --rm --name my-running-app my-php-app
For many simple, single file projects, you may find it inconvenient to write a complete Dockerfile
. In such cases, you can run a PHP script by using the PHP Docker image directly:
$ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp php:5.6-cli php your-script.php
More commonly, you will probably want to run PHP in conjunction with Apache httpd. Conveniently, there's a version of the PHP container that's packaged with the Apache web server.
FROM php:5.6-apache
COPY src/ /var/www/html/
Where src/
is the directory containing all your php code. Then, run the commands to build and run the Docker image:
$ docker build -t my-php-app .
$ docker run -d --name my-running-app my-php-app
We recommend that you add a custom php.ini
configuration. COPY
it into /usr/local/etc/php
by adding one more line to the Dockerfile above and running the same commands to build and run:
FROM php:5.6-apache
COPY config/php.ini /usr/local/etc/php/
COPY src/ /var/www/html/
Where src/
is the directory containing all your php code and config/
contains your php.ini
file.
We provide the helper scripts docker-php-ext-configure
, docker-php-ext-install
, and docker-php-ext-enable
to more easily install PHP extensions.
For example, if you want to have a PHP-FPM image with iconv
, mcrypt
and gd
extensions, you can inherit the base image that you like, and write your own Dockerfile
like this:
FROM php:5-fpm
RUN apt-get update && apt-get install -y \
libfreetype6-dev \
libjpeg62-turbo-dev \
libmcrypt-dev \
libpng12-dev \
&& docker-php-ext-install -j$(nproc) iconv mcrypt \
&& docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ \
&& docker-php-ext-install -j$(nproc) gd
Remember, you must install dependencies for your extensions manually. If an extension needs custom configure
arguments, you can use the docker-php-ext-configure
script like this example.
Some extensions are not provided with the PHP source, but are instead available through PECL. To install a PECL extension, use pecl install
to download and compile it, then use docker-php-ext-enable
to enable it:
FROM php:5-fpm
RUN apt-get update && apt-get install -y libmemcached-dev \
&& pecl install memcached \
&& docker-php-ext-enable memcached
Some extensions are not provided via either Core or PECL; these can be installed too, although the process is less automated:
FROM php:5-apache
RUN curl -fsSL 'https://xcache.lighttpd.net/pub/Releases/3.2.0/xcache-3.2.0.tar.gz' -o xcache.tar.gz \
&& mkdir -p xcache \
&& tar -xf xcache.tar.gz -C xcache --strip-components=1 \
&& rm xcache.tar.gz \
&& ( \
cd xcache \
&& phpize \
&& ./configure --enable-xcache \
&& make -j$(nproc) \
&& make install \
) \
&& rm -r xcache \
&& docker-php-ext-enable xcache
If you don't want to include a Dockerfile
in your project, it is sufficient to do the following:
$ docker run -d -p 80:80 --name my-apache-php-app -v "$PWD":/var/www/html php:5.6-apache
The php
images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on the popular Alpine Linux project, available in the alpine
official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as git
or bash
) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine
image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
This image is officially supported on Docker version 1.11.2.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
Documentation for this image is stored in the php/
directory of the docker-library/docs
GitHub repo. Be sure to familiarize yourself with the repository's README.md
file before attempting a pull request.
If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker
issue on the official-images
repository first.
You can also reach many of the official image maintainers via the #docker-library
IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.