Wordpress-Image: choice of WP version with multistage build

[designzwang]

Hi,

I like having a combined Apache-FPM image for wordpress, so I want to use your very useful pre-build wordpress image(s) .

However we need to be able to not only chose the PHP version, but also use different WP versions, and we need to enable additional modules for php and install some additional tools.

My plan is to use a multistage build with the original Wordpress images as a source and copy the WP files from the official image into /var/www/html of your FPM image.

That way, we will have an image that already has the desired php and wordpress version , and then we have the choice, depending on the project, to either use the provided version of the image or mount a project specific tree into /var/www/html.

On first sight it works fine - or do you see any problems when we do this?
The dockerfile is attached below.
Regards,
Uli

# Dockerfile for adding a specific WP version into shinsenter FPM WP image
# in this example, values are hardcoded - actually they will be set by Jenkins at build time
ARG KDEPHP=8.1
ARG KDEWP=6.8

# we need both wordpress (for official wordpress files in specific versions) and fpm Image from shinsenter  :
ARG WP_FPM_IMAGE=our-repo.example.com/dockerhub-proxy/shinsenter/wordpress:php${KDEPHP}
ARG WP_OFFICIAL_IMAGE=our-repo.example.com/dockerhub-proxy/library/wordpress:${KDEWP}-php${KDEPHP}-apache

# alias for copying matching WP files from offical image
FROM ${WP_OFFICIAL_IMAGE} AS wordpress_files
ENV KDEPHP=$KDEPHP
ENV KDEWP=$KDEWP

# clean out plugins and themes to make space for our own collection
RUN rm -r /usr/src/wordpress/wp-content/plugins/* \
    && rm -r /usr/src/wordpress/wp-content/themes/* \
    && ( cp /usr/src/wordpress/wp-config-docker.php /usr/src/wordpress/wp-config-docker-dist.php || true ) \
    && touch /usr/src/wordpress/transferred-from-wp-original-src-by-ncs-Dockerfile-build

# shinsenter fpm is our real base image
FROM ${WP_FPM_IMAGE}
ENV KDEPHP=$KDEPHP
ENV KDEWP=$KDEWP

COPY --from=wordpress_files /usr/src/wordpress /var/www/html

# install or enable other tools needed. Not all apache modules are enabled by default, better do that
RUN apt-get update && \
 phpaddmod imagick bz2 && \
 apt-get update && apt-get install -y git curl mariadb-client ssmtp libz-dev less vim sudo gettext &&  \
 rm -rf /var/lib/apt/lists/* && \
  apt-get clean && \
 a2enmod access_compat alias auth_basic authn_core authn_file authz_core authz_host authz_user deflate dir env expires filter mime negotiation remoteip reqtimeout rewrite setenvif status && \
 sed -i 's/# RemoteIPTrustedProxy/RemoteIPInternalProxy /ig' /etc/apache2/apache2.conf

[shinsenter]

Hi @designzwang

Thank you for trusting and using my Docker images for your WordPress projects. I think it’s great that you’re able to freely customize the WordPress environment to suit your specific needs. I don’t have any particular comments, as I think your setup is already excellent since it’s working as expected.

If I may suggest, consider running the cleanup command at the end of the same RUN instruction where you install additional modules or software.

Best regards!

[shinsenter]

By the way, if you use Docker images based on the Alpine variant, you may be able to further optimize the file size of your Docker images.

[designzwang]

Thank you @shinsenter for checking my suggestion, and doing it so quickly. So I will try this with a small site in production and see how it works, and how we can deal with the combined output of FPM and Apache. Regarding alpine - that might certainly be a good way to trim down the image, so I will check whether everything we need is in there. Using Debian just feels comfortable ;)
Thanks again and best regards
Uli
( I am not sure whether to close this discussion or not - if you want I could add some comments later how things worked out for people trying something similar )

[shinsenter]

@designzwang
I think it could be useful for others, so you don’t need to worry about closing this discussion. 😉

[designzwang]

Alright :) so lets discuss ... just to let you know how your suggestion with alpine came out.

Using your alpine build out of the box would be quite small indeed, half the size of the FPM/WP debian image. But after adding image magick and some tools, the final images are 1.1 GB in both cases (i.e. with alpine or debian base).

# list of docker images shin-Alpine
docker images | grep alpine
REPOSITORY                                                              TAG              IMAGE ID       CREATED         SIZE
# out of the box image size alpine:
harbor.example.com/dockerhub-proxy/shinsenter/wordpress               php8.1-alpine            82e424a7c37e   7 days ago      155MB
# plus apk packages git curl  mariadb-client ssmtp zlib-dev less vim sudo gettext 
harbor.example.com/nexusclone/ncs-cms-wordpress                       develop-alpine           57c8a3ba4210   5 minutes ago   601MB
# apk added tools plus "phpaddmod imagick bz2"
harbor.example.com/nexusclone/ncs-cms-wordpress                       develop-alpine-imagick   b155b6b50337   2 hours ago     1.04GB

So using phpaddmod for php-imagemagick and bz2 adds another 400MB on top of the additional 400 MB the needed tools have.
I am aware that phpaddmod is not your software, but just a wrapper. I found a cleanup option in the source, but
they claim:

WARNING the --cleanup option is deprecated (we always cleanup everything)

I should go and check the issue queue of the project and maybe ask why cleanup seems not to work properly, I guess there is nothing you can do about this.
Regards
uli

[shinsenter]

I meant the command named cleanup that's included in my Docker images, not the --cleanup option.