readystack/grafana repository overview

⁠Grafana

readystack/grafana:v13.3.0-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of github.com/grafana/grafana v13.3.0 (AGPL-3.0-only), built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠Who uses it and why

Who: Operations, SRE and development teams who need dashboards and alerts over their metrics, logs and traces.

Why: Grafana queries, visualises and alerts on metrics, logs and traces wherever they are stored, and lets teams build and share dashboards that mix several data sources.

Use case: An operations team keeps server metrics in one database and application logs in another. A Grafana dashboard shows both for each service, an alert rule notifies the on-call engineer when errors climb, and the engineer moves from the graph to the matching logs with the same filters.

About the upstream project, written from its own description: https://github.com/grafana/grafana⁠ · https://grafana.com/docs/grafana/latest/introduction/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:743df6d5955bcf09c4d5fb479299640a8324b9ccbd8ff01c83adc37c623abf2d on 2026-10-30.

• 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/grafana⁠
• 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:743df6d5955bcf09c4d5fb479299640a8324b9ccbd8ff01c83adc37c623abf2d; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/grafana:v13.3.0-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (grafana).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v13.3.0-CE-ubuntu24.04-r1 — 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/grafana:v13.3.0-CE-ubuntu24.04-r1

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

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

⁠Deployment

Single container, single static Go binary (CGO-free) + on-disk web frontend (public/) served from --homepath, foreground process. Observability/dashboards platform. State lives in an EMBEDDED SQLite database at /var/lib/grafana/grafana.db that grafana creates + migrates itself on first boot — NO external/relational DB, no docker-compose, no Kubernetes. The image holds the complete Grafana server but not its data-source and app plugins: on its first start Grafana downloads them (Prometheus, Loki, PostgreSQL, MySQL, Elasticsearch, CloudWatch and others, about 600 MB) from grafana.com into /var/lib/grafana/plugins, and without internet access it starts with only its four built-in data sources (Alertmanager, Azure Monitor, Graphite and TestData). (Grafana CAN be pointed at an external Postgres/MySQL via GF_DATABASE_* env, but the default + this image's self-contained shape is embedded SQLite.)

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 grafana.env with install -m 600 /dev/null grafana.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: Grafana gives the first admin the GF_SECURITY_ADMIN_PASSWORD below when it creates that admin. Remove this line after setup and recreate the container; the admin keeps the password.
GF_SECURITY_ADMIN_PASSWORD=YOUR_STRONG_SECRET

docker run -d --name grafana -p 3000:3000 --env-file ./grafana.env -v grafana-data:/var/lib/grafana readystack/grafana:v13.3.0-CE-ubuntu24.04-r1

Sign in at http://localhost:3000⁠ as admin with the password from grafana.env. Once the first start has created the admin, remove the GF_SECURITY_ADMIN_PASSWORD line from grafana.env and recreate the container on the same volume (docker rm -f grafana, then the docker run command again): Grafana reads the variable only when it creates the admin, so the admin keeps its 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 the password into /var/lib/grafana/initial_admin_password instead (see Administrator password in the handbooks).

⁠Source changes (AGPL)

This software is licensed under the GNU Affero General Public License, and the releases below are built from a modified copy of its source. Each line names a release, what ReadyStack changed and where the diff is published. From 2026-10-27 a release's diff carries every upstream file its build changes, the dependency manifests and lockfiles included, so its complete corresponding source is the upstream tag with that diff applied; the diff of an earlier release carries the source edits its line names, and the dependency files that release's build changed are in its release archive (vendored/). If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source; for a release from 2026-10-27 on, a link to its diff and the upstream tag does that.

• v13.3.0-CE-ubuntu24.04-r1 — the Go workspace files go.work and go.work.sum are deleted so the root module vendors and builds alone (its go.mod replace directives keep every in-tree module the server uses), and the build raises Go-module dependency versions in go.mod and go.sum where upstream's are older than the fixed, upstream-published releases (security updates; no Grafana source file is edited); full diff of every upstream file the build changes at https://readystack.dev/source/grafana/v13.3.0/grafana-v13.3.0-readystack.patch⁠
• v13.2.4-CE-ubuntu24.04-r2 — the Go workspace files go.work and go.work.sum are deleted so the root module vendors and builds alone (its go.mod replace directives keep every in-tree module the server uses), and go.mod/go.sum raise github.com/getkin/kin-openapi to v0.149.0 (with github.com/santhosh-tekuri/jsonschema/v6 v6.0.3) for security fixes; full diff at https://readystack.dev/source/grafana/v13.2.4/grafana-v13.2.4-readystack.patch⁠
• v13.2.4-CE-ubuntu24.04-r1 — the Go workspace files go.work and go.work.sum are deleted so the root module vendors and builds alone (its go.mod replace directives keep every in-tree module the server uses), and go.mod/go.sum raise github.com/getkin/kin-openapi to v0.149.0 (with github.com/santhosh-tekuri/jsonschema/v6 v6.0.3) for security fixes; full diff at https://readystack.dev/source/grafana/v13.2.4/grafana-v13.2.4-readystack.patch⁠

⁠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/grafana⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:fb27f09a89c9f78502cb62ddf439cb2ce41baa3f4d26f15f105d088cc9f24e38 on 2026-10-29.

— ReadyStack · readystack.dev