readystack/nextcloud repository overview

⁠Nextcloud

readystack/nextcloud:v35.0.2-CE-ubuntu24.04-r3

A cosign-signed build of github.com/nextcloud/server v35.0.2 (AGPL-3.0-or-later), built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:4da45c89cfd9b2d6f0711cee8a8c6e6c8a739c4c35111461d362ef1837e7b662 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.html#nextcloud⁠
• 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:4da45c89cfd9b2d6f0711cee8a8c6e6c8a739c4c35111461d362ef1837e7b662; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/nextcloud:v35.0.2-CE-ubuntu24.04-r3.
• 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 v35.0.2-CE-ubuntu24.04-r3 — the release on sale 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/nextcloud:v35.0.2-CE-ubuntu24.04-r3

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

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

⁠Deployment

Single container (Apache + mod_php, one foreground process) running Nextcloud Server. SELF-CONTAINED: the database is a self-managed EMBEDDED SQLite file (owncloud.db) under /var/www/html/data — the image IS the complete running instance, no external DB and no sidecar required. (The image contains only the SQLite database driver; it cannot be pointed at an external MySQL/MariaDB or PostgreSQL database.) NOT a multi-service cluster, NOT docker-compose/Kubernetes-only.

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 nextcloud.env with install -m 600 /dev/null nextcloud.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 Nextcloud and creates the administrator (NEXTCLOUD_ADMIN_USER) with NEXTCLOUD_ADMIN_PASSWORD. Remove this line after setup and recreate the container; the administrator keeps the password.
NEXTCLOUD_ADMIN_PASSWORD=YOUR_STRONG_PASSWORD

docker run -d --name nextcloud -p 8080:8080 -e NEXTCLOUD_ADMIN_USER=admin --env-file ./nextcloud.env -e NEXTCLOUD_TRUSTED_DOMAINS='localhost 127.0.0.1 cloud.example.com' -v nextcloud-data:/var/www/html/data -v nextcloud-config:/var/www/html/config readystack/nextcloud:v35.0.2-CE-ubuntu24.04-r3

Or leave out NEXTCLOUD_ADMIN_USER and the env file and complete the web setup wizard on first visit. Once the first start has installed Nextcloud, remove the NEXTCLOUD_ADMIN_PASSWORD line from nextcloud.env and recreate the container on the same volumes (docker rm -f nextcloud, then the docker run command again): the administrator keeps the password, and the password is no longer in the container's environment (tested).

⁠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; the complete corresponding source is the upstream tag with that diff applied, as the notice beside the diff explains. If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source: a link to the diff and the upstream tag does that.

• v35.0.2-CE-ubuntu24.04-r3 — the build deletes tests/, build/, .github/, .devcontainer/, contribute/, .idea/ and .tx/ (1,326 files a running server does not use, all listed in upstream's own .nextcloudignore as files removed at build time); full diff at https://readystack.dev/source/nextcloud/v35.0.2/nextcloud-v35.0.2-readystack.patch⁠
• v35.0.2-CE-ubuntu24.04-r2 — the build deletes tests/, build/, .github/, .devcontainer/, contribute/, .idea/ and .tx/ (1,326 files a running server does not use, all listed in upstream's own .nextcloudignore as files removed at build time); full diff at https://readystack.dev/source/nextcloud/v35.0.2/nextcloud-v35.0.2-readystack.patch⁠
• v35.0.2-CE-ubuntu24.04-r1 — the build deletes tests/, build/, .github/, .devcontainer/, contribute/, .idea/ and .tx/ (1,326 files a running server does not use, all listed in upstream's own .nextcloudignore as files removed at build time); full diff at https://readystack.dev/source/nextcloud/v35.0.2/nextcloud-v35.0.2-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 at readystack.dev/buy.html⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:e0ece9b979454f47790449aa44ce89ff1efffedd7f6ca4c137581cf00c88fd37 on 2026-10-27.

— ReadyStack · readystack.dev