readystack/wordpress repository overview

⁠WordPress

readystack/wordpress:7.1.3-CE-ubuntu24.04-r4

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/wordpress/recipe⁠
• Upstream source at this release's pinned commit (7.1.3): https://github.com/WordPress/WordPress/tree/fc9832bef919c2a08541248db23af90d14ffb082⁠
• Product page: https://readystack.dev/products/wordpress⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/wordpress⁠
• Release history (JSON): https://readystack.dev/api/releases/wordpress⁠
• Defect record: https://readystack.dev/defects.html?product=wordpress⁠
• Today's scan: https://readystack.dev/products/wordpress#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=wordpress⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/WordPress/WordPress 7.1.3 (GPL-2.0-or-later), WordPress.org's Git mirror of the WordPress core release builds, with WordPress.org's SQLite Database Integration 3.0.2 (github.com/WordPress/sqlite-database-integration, GPL-2.0-or-later) as the default database layer, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Bloggers, small businesses, publishers and organisations who build and run websites.

Why: WordPress is open-source publishing software for websites and blogs. Write and schedule posts and pages, manage media and users with roles, and extend the site with themes and plugins.

Use case: A local business wants a website its staff can update without a developer. With WordPress they pick a theme, the owner writes and schedules news posts, an editor manages the pages and images, and plugins add a calendar and spam protection for comments.

About the upstream project, written from its own description: https://wordpress.org/about/⁠ · https://wordpress.org/about/features/⁠ · https://github.com/WordPress/WordPress⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:1ec45521c497c664e603ccd1f5e8b367fa41cc68b9597b0a4a64261a3d4e2083 on 2026-10-27.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/wordpress⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:1ec45521c497c664e603ccd1f5e8b367fa41cc68b9597b0a4a64261a3d4e2083; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/wordpress:7.1.3-CE-ubuntu24.04-r4.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (www-data).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 7.1.3-CE-ubuntu24.04-r4 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/wordpress:7.1.3-CE-ubuntu24.04-r4

# ✗ unsupported (do not pull)
docker pull readystack/wordpress:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/wordpress:7.1.3-CE-ubuntu24.04-r4 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container: Apache with mod_php, one foreground process, running WordPress 7.1.3 as www-data (uid 33) on port 8080. Self-contained by default: the database is an embedded SQLite file on the wordpress-data volume, through WordPress.org's SQLite Database Integration drop-in, so no database server and no second container are needed. Set WORDPRESS_DB_HOST and WORDPRESS_DB_PASSWORD (WORDPRESS_DB_NAME and WORDPRESS_DB_USER default to wordpress) to use your own MySQL or MariaDB server instead, the databases WordPress itself is built for. WordPress is installed by the container at its first start; the web installer is never served.

Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create wordpress.env with install -m 600 /dev/null wordpress.env, then write these lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.

# First start only: the first start installs WordPress and creates the administrator (WORDPRESS_ADMIN_USER) with WORDPRESS_ADMIN_PASSWORD. Remove this line after setup and recreate the container; the administrator keeps the password.
WORDPRESS_ADMIN_PASSWORD=YOUR_ADMIN_PASSWORD

docker run -d --name wordpress -p 8080:8080 -e WORDPRESS_URL=http://localhost:8080 -e WORDPRESS_ADMIN_USER=admin -e [email protected] --env-file ./wordpress.env -v wordpress-content:/var/www/html/wp-content -v wordpress-data:/var/lib/wordpress readystack/wordpress:7.1.3-CE-ubuntu24.04-r4

Set WORDPRESS_URL to the exact address people will open, for example https://blog.example.com⁠ behind your TLS proxy: WordPress builds every link and redirect from it. Once the first start has installed WordPress, remove the WORDPRESS_ADMIN_PASSWORD line from wordpress.env and recreate the container on the same volumes (docker rm -f wordpress, then the docker run command again): the administrator keeps the password, and the password is no longer in the container's environment (tested). Leave the line out from the start and the first start generates a password into /var/lib/wordpress/initial_admin_password instead.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/wordpress⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:9e32ef4f20c508f445b5ed93248aa204e19393494f8557956d86fb9b3f72797a on 2026-10-27.

— ReadyStack · readystack.dev

⁠Tags no longer offered

These tags are on Docker Hub but ReadyStack does not offer them. They are kept so existing pulls do not break, but they are unsupported and receive no security updates; do not use them in production. Use the current release named on this page.

• 7.1.3-CE-ubuntu24.04-r1 — pushed to Docker Hub on 2026-10-17 before the final release gate, which then refused it (Ubuntu apache2 2.4.58-1ubuntu8.17 security fix, published after it was built); never on sale; the fixed build will be 7.1.3-CE-ubuntu24.04-r2 (labelled 2026-10-20)