Containerization of PHP Applications with Docker: A Complete Developer's Guide

Why Every PHP Developer Should Master Docker?

Have you ever encountered a situation where everything works perfectly locally, but on the server you get a "white screen of death"? Or, even worse, when a colleague says: "It works for me, just update composer" — and your project turns into a pumpkin? Sound familiar? Then welcome to the world of containerizing PHP applications with Docker.

Docker is not just a trendy buzzword. It's a tool that will forever change your approach to development. Imagine: you no longer spend hours setting up the environment. No need to install XAMPP, OpenServer, or struggle with PHP versions. One docker-compose up — and your application lives in an isolated, predictable world. And this world can be shared with a colleague, deployed to a server, or even sold to a client. In this article, we'll break down containerization of PHP applications from A to Z: from a basic Dockerfile to production optimization.

What is Containerization and Why Does PHP Need It?

Containerization is a way to package an application together with all its dependencies (PHP, extensions, web server, database) into an isolated environment — a container. Unlike virtual machines, containers are lightweight, start in seconds, and consume minimal resources.

This is especially relevant for PHP. Why? Because a typical PHP application is a bundle: PHP-FPM, Nginx or Apache, MySQL/PostgreSQL, Redis, a task queue. Manually configuring this ecosystem on every machine is a nightmare. But with Docker, you describe the entire infrastructure in code (Infrastructure as Code) and reproduce it with a single command.

Key Benefits of Containerization for a PHP Developer:

\n
• Environment Consistency: local environment = staging = production. Forget about "it works on my machine".
\n
• Dependency Isolation: a project on PHP 7.4 can peacefully coexist with a project on PHP 8.3 on the same host computer.
\n
• Fast Deployment: just push the image to a registry and update the container on the server.
\n
• Scalability: easily add another PHP-FPM container under load.
\n

Creating Your First Dockerfile for a PHP Application

Let's start with the most important part — the Dockerfile. This is the instruction for building the image of your application. Let's assume we have a simple PHP application on Laravel or Symfony (the principle is the same for any framework).

# Use the official PHP 8.2 image with FPM\nFROM php:8.2-fpm-alpine\n\n# Install system dependencies\nRUN apk add --no-cache \\\n    nginx \\\n    supervisor \\\n    libpng-dev \\\n    libjpeg-turbo-dev \\\n    freetype-dev \\\n    && docker-php-ext-configure gd --with-freetype --with-jpeg \\\n    && docker-php-ext-install -j$(nproc) pdo_mysql gd opcache\n\n# Copy configs\nCOPY ./docker/nginx.conf /etc/nginx/http.d/default.conf\nCOPY ./docker/supervisord.conf /etc/supervisor/conf.d/supervisord.conf\nCOPY ./docker/php.ini /usr/local/etc/php/conf.d/custom.ini\n\n# Install Composer\nCOPY --from=composer:latest /usr/bin/composer /usr/bin/composer\n\n# Copy application source code\nCOPY . /var/www/html\nWORKDIR /var/www/html\n\n# Install PHP dependencies\nRUN composer install --no-dev --optimize-autoloader\n\n# Set permissions\nRUN chown -R www-data:www-data /var/www/html/storage /var/www/html/bootstrap/cache\n\nEXPOSE 80\n\nCMD ["supervisord", "-c", "/etc/supervisor/conf.d/supervisord.conf"]

Breaking it down:

\n
• FROM php:8.2-fpm-alpine — we take a lightweight image based on Alpine Linux. It weighs ~50 MB instead of 200+ MB for desktop images.
\n
• docker-php-ext-install — a magic command for installing PHP extensions directly inside the container.
\n
• COPY --from=composer:latest — multi-stage build. We take the ready-made Composer binary from the official image, without installing PHP separately.