PHP 5.6 & Apache Dockerfile Example

A base PHP 5.6 Apache 2 image¹ for demonstrating legacy projects available at EWC Docker Hub.

An older version of PHP that some older codebase sites would require as an environment to run in.

Other Packages Included:

• Node v8.x
• Composer v1.7.1
• libxml2-dev
• libzip-dev
• libyaml-dev
• zip
• unzip
• git
• nodejs
• default-mysql-client
• vim
• npm i npm@$NPM_VERSION² -g
• yaml-1.3.0

PHP Extensions:

• gettext
• mysqli
• pdo_mysql
• zip
• yaml

Build & Compose Up

Note that the php-5-6-apache is the Docker Compose Service to Build.

There is a build script included that uses the local .env file & an Evil Wizard Creations Protocol that makes this much simpler.

build-up-php-5-6-apache.sh

Alternatively there is the full Procedure.

1. Build the Image using the docker-compose-build.yaml configuration.

   docker-compose -f ./docker-compose-build.yaml build --no-cache php-5-6-apache

2. Compose Up using the docker-compose-build.yaml configuration will use the new built Image and -d to detach.

   docker-compose -f ./docker-compose-build.yaml up -d

Build Image The Long Way

Build the Docker Image without using cached versions of previous image build stages.

sudo docker build \
    -f php-5-6-apache.Dockerfile \
    --target build-php-56-apache \
    --build-arg APP_ENV=local \
    --build-arg NPM_VERSION=6.4.1 \
    --no-cache \
    -t php-5-6-apache:latest \
    .

N.B.

• Using -f php-5-6-apache.Dockerfile

  To specify php-5-6-apache.Dockerfile as the filename to build otherwise it is expected to be named just Dockerfile.

• Using --target build-php-56-apache

  To select the build target stage³ from the Dockerfile.

• Using --no-cache

  To prevent using previous cached versions of image build stages.

• Using --build-arg NPM_VERSION=6.4.1

  To set build arguments & values to use during the build process. NPM_VERSION=6.4.1 sets the Node Version to be used to 6.4.1 when rebuilding the image.

• Using -t php-5-6-apache:latest

  To name & tag the locally built docker image.

• Using .

  To set the current location as the build context for the build process.

Create A Container

This creates a named container and attaches it to the host network and may cause port conflict if the host machine is already listening on any exposed ports from the Docker Image being used.

sudo docker run \
    -d \
    --network host \
    -v "$(pwd)"/public_html:/var/www/html \
    --name php-5-6-apache \
    php-5-6-apache:latest

OR

This creates a named container and attaches it to the bridge network and allows for port forward mapping from the host to the Container.

sudo docker run \
    -d \
    --network bridge \
    -p 8080:80/tcp \
    -v "$(pwd)"/public_html:/var/www/html \
    --name php-5-6-apache \
    php-5-6-apache:latest

N.B.

• Using -v "$(pwd)"/public_html:/var/www/html

  To Volume Mount the folder public_html from the current folder to /var/www/html on the running container. It is where Apache serves the content from & allows for realtime change updates.

• Using -p 8080:80/tcp

  To map port 8080 on the Host machine to port 80 on the Container using the bridge network.

• Using --name php-5-6-apache

  To name the Container being created.

Start Container

sudo docker start php-5-6-apache

Stop Container

sudo docker stop php-5-6-apache

Connect To Container

sudo docker exec -it php-5-6-apache /bin/bash

Disclaimer

This Apache2 + PHP 5.6 build environment should NOT be used anywhere near a production environment. This build is for showcasing legacy systems that simple would not run in modern environments & as such it is littered with security holes and exploitation's.

Footnotes

1. Use docker pull ewc2020/web:php-5.6-apache-latest to get a copy of the image. ↩

2. Uses a .env build-arg called NPM_VERSION to specify the npm version. ↩

3. Used mostly in Multi Stage image builds. ↩