readystack/portainer repository overview

⁠Portainer

readystack/portainer:2.45.3-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of github.com/portainer/portainer v2.45.3 (Zlib), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Homelab operators, hobbyists, students and anyone experimenting with containers on their own hardware.

Why: Portainer Community Edition is a free, lightweight web interface for managing containers on container hosts and Kubernetes.

Use case: A hobbyist runs many self-hosted apps on a home server and loses track of them on the command line. Portainer shows every container on one web page, where they view its logs and statistics, open its console, and edit or remove it with a few clicks.

About the upstream project, written from its own description: https://github.com/portainer/portainer⁠ · https://docs.portainer.io/user/docker/containers⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:ced8888be99cd55db0efe6913a5ea8b0face53310fa0b58fbd87671798d7b0a1 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/portainer⁠
• 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:ced8888be99cd55db0efe6913a5ea8b0face53310fa0b58fbd87671798d7b0a1; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/portainer:2.45.3-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (portainer).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

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

• 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/portainer:2.45.3-CE-ubuntu24.04-r1

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/portainer:2.45.3-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, one static CGO-free Go binary (portainer) that serves a web UI + a REST API + an Edge reverse-tunnel server, all in one foreground process. Portainer is a container-management GUI for Docker / Docker Swarm / Kubernetes. ALL state - users, environments, stacks, settings, edge configs - lives in an EMBEDDED bbolt key-value database at /data/portainer.db that the server creates + migrates itself; NO external/relational DB, NO docker-compose, NO sidecar. The on-disk web frontend (dist/public) is served from /opt/portainer/public. The image IS the complete running instance.

docker run -d --name portainer -p 9000:9000 -p 9443:9443 -v portainer-data:/data -v /var/run/docker.sock:/var/run/docker.sock --group-add $(stat -c %g /var/run/docker.sock) readystack/portainer:2.45.3-CE-ubuntu24.04-r1

--group-add gives Portainer, which runs as the non-root user portainer (uid 999), the group that owns the host's Docker socket; with the socket mount alone it gets permission denied and cannot add the local environment. Leave out both the socket mount and --group-add if this Portainer should not manage the host it runs on. Add -p 8000:8000 only if remote Edge Agents must reach this instance.

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

— ReadyStack · readystack.dev