readystack/mysql repository overview

⁠MySQL

readystack/mysql:9.7.4-CE-ubuntu24.04-r4

Source, recipe and records

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

A cosign-signed build of github.com/mysql/mysql-server tag mysql-9.7.4 (MySQL 9.7.4, a release of the 9.7 LTS series; GPL-2.0 with Oracle's additional permissions, see the LICENSE file at that tag), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Developers and database administrators who need a relational SQL database for web and business applications.

Why: MySQL is a relational database server. Data lives in tables that applications add to, query and change with SQL, through a wide range of client libraries and APIs.

Use case: An online store keeps its products, customers and orders in MySQL tables. The web application reads and writes them with SQL through a client library for its language, and administrators manage the server, its users and its databases with MySQL's own tools.

About the upstream project, written from its own description: https://github.com/mysql/mysql-server⁠ · https://dev.mysql.com/doc/refman/8.4/en/what-is-mysql.html⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:88d405398740090db849f2526e2af059daa4971b069c6bd33aac7dd081c4251c on 2026-11-10.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/mysql⁠
• ReadyStack release check — passed at release on 2026-11-09: 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:88d405398740090db849f2526e2af059daa4971b069c6bd33aac7dd081c4251c; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/mysql:9.7.4-CE-ubuntu24.04-r4.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (mysql).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 9.7.4-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.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• 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/mysql:9.7.4-CE-ubuntu24.04-r4

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/mysql:9.7.4-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. MySQL Community Server 9.7.4 (9.7 LTS) compiled from the upstream source tag with CMake and installed in /usr/local/mysql. The image is the whole database server: there is no external database and no sidecar. mysqld runs in the foreground as the non-root mysql user. On the first start with an empty data directory the entrypoint creates the data directory in /var/lib/mysql and sets the root password before the server opens a network port.

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 mysql.env with install -m 600 /dev/null mysql.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: MYSQL_ROOT_PASSWORD sets root's password when the first start initialises an empty data directory. Remove this line after setup and recreate the container; root keeps the password.
MYSQL_ROOT_PASSWORD=YOUR_ROOT_PASSWORD

docker run -d --name mysql --env-file ./mysql.env -p 3306:3306 -p 33060:33060 -v mysql-data:/var/lib/mysql readystack/mysql:9.7.4-CE-ubuntu24.04-r4

Replace YOUR_ROOT_PASSWORD in mysql.env with a password of at least 8 characters, written as it is: docker reads the line literally, so spaces and characters such as $ or ! need no quotes (and quotes would become part of the password). On an empty data directory the image refuses to start without one, and refuses the placeholder itself. Once the first start has initialised the data directory, remove the MYSQL_ROOT_PASSWORD line from mysql.env and recreate the container on the same volume (docker rm -f mysql, then the docker run command again): the server starts, root keeps its password, and the password is no longer in the container's environment (tested).

⁠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/mysql⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:9a2c5adf1c8995e997e4ed346254358c940ea3e8b79d14a746a81a5deb4edeba on 2026-11-09.

⁠Trademarks

This image contains MySQL®.

Oracle, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

ReadyStack is not affiliated with or endorsed by Oracle and/or its affiliates.

The name identifies the software in this image; it is built from github.com/mysql/mysql-server source at mysql-9.7.4 (commit 780b506e8296). ReadyStack does not modify its source.

ReadyStack uses no project logos.

Trademark policy: https://www.oracle.com/legal/trademarks.html⁠ (read 2026-11-04).

— ReadyStack · readystack.dev