Skip to content
 
 

Repository files navigation

dockerpress-base-image

A great base image for WordPress sites.

Usage

The base image is available on both Docker Hub.

We provide multiple tags for images, below are some common examples:

# To use a specific semantic version
FROM evermadefi/dockerpress-base-image:3.0.14
FROM evermadefi/dockerpress-base-image:3.0
FROM evermadefi/dockerpress-base-image:3

# You can specify the Debian and PHP versions as well
FROM evermadefi/dockerpress-base-image:3.0.14-php8.3-debian13
FROM evermadefi/dockerpress-base-image:3.0.14-php8.3
FROM evermadefi/dockerpress-base-image:3.0.14-debian13

# To use a specific tag or branch
FROM evermadefi/dockerpress-base-image:v3.0.14
FROM evermadefi/dockerpress-base-image:master

# To use a specific commit hash
FROM evermadefi/dockerpress-base-image:deadbeefdeadbeefdeadbeefdeadbeefdeadbeef

To simply just pull the image or update a stale local copy, run the docker pull command like so with the tag you wish you pull:

docker pull evermadefi/dockerpress-base-image:3.0.14

And enjoy!

Contributing

  1. Commit any necessary changes to the Dockerfile on your branch

  2. Create a pull request to the appropriate branch (such as master) from your branch

  3. Make sure your pull request passes the automatic build workflow and fix appropriately if needed

  4. Request a pull request review

  5. Have the pull request approved and merged to master

  6. Once merged to master, a new build process will be automatically dispatched and once complete, the new image will be pushed to container registries with both the long and short commit hash and branch name as tags. The build process also automatically applies Open Containers labels to the images.

Publishing a new version

  1. Draft a new release on GitHub using the MAJOR.MINOR.PATCH semantic versioning scheme for the new tag with the "v" prefix (e.g. v3.0.99). You can also create and push a tag separately using your preferred Git client, but GitHub allows you to do this all at once, so it is not necessary.

  2. Write a description with the changelog for the release.

  3. Publish the new release

  4. This automatically triggers the image builder GitHub Workflow and will eventually, after some 30 minutes, push the new images with the appropriate tags and labels to Docker Hub. So, go get a cup of ☕️ while you wait.

  5. Once the build is complete, you can pull the new image as shown in the Usage section. Sometimes a build may fail due to rate limiting. You should trigger a rebuild for a failed build manually. You don't need to rebuild everything, just the failed builds.

Templates

The Dockerfiles and GitHub Actions workflows are templated with Nunjucks (.njk files).

If you want to edit a Dockerfile or workflow please edit the corresponding template file and then run node generate-files.js to generate the final files. Do not edit any generated files directly.

Adding third party downloads

  1. Check the integrity of the source yourself, that the contents are correct.

  2. Install an ADD instruction with the checksum and appropriate owner and permissions.

  3. If available, verify the file signatures with a known good GPG key.

If the build is throwing a checksum mismatch error, the file contents must have changed and must be re-verified.

If the signature cannot be verified, the file is not signed by a known good GPG key. If the GPG key used to sign the file looks valid, you should add it to the GPG key list.

Updating Python packages

Python is currently used by certbot (certbot-requirements.in) and supervisor (supervisor-requirements.in).

  1. Additional dependencies may be added to the *-requirements.in file if required.

  2. Run the Docker command commented in *-requirements.in to generate the *-requirements.txt file.

  3. Verify that the *-requirements.txt is legit.

Dependency checklist

The following dependencies should be checked every so often for updates.

Actions

Dockerfile

Releases

Contributors

Languages