vedla/cloudreve repository overview

⁠Cloudreve Docker

Advantages

• Based on Cloudreve V4⁠
• Long-term maintenance
• Multiple version tags available, so you can pin the exact Cloudreve release you want
• Alpine-based runtime, built from the official prebuilt binaries
• Multi-architecture support (amd64, arm64, arm/v7)
• Easy to set up
• Optional Aria2 support for offline downloads (no separate container required when enabled)
• Detailed Cloudreve + Nginx deployment guide included

⁠Available tags

• <version> (e.g. 4.17.0): a specific pinned Cloudreve v4 release
• 4: always points at the newest Cloudreve v4 release published by this project
• latest: same as 4

See the full list of published versions on Docker Hub⁠.

⁠Getting started

Directories

• <PATH TO data>: data directory that stores the config, database, avatars, uploads, and Aria2 downloads, e.g. /dockercnf/cloudreve/data

Create the data directory

mkdir -p <PATH TO data>

Build an ARMv7 image locally

docker buildx build --platform linux/arm/v7 \
  --build-arg CLOUDREVE_VERSION=4.17.0 \
  --build-arg INSTALL_ARIA2=0 \
  -t cloudreve:armv7 \
  --load .

Start the Cloudreve container

docker run -d \
  --name cloudreve \
  -e TZ="America/Toronto" \
  -e CR_ENABLE_ARIA2=0 \
  -p 5212:5212 \
  --restart=unless-stopped \
  -v <PATH TO data>:/cloudreve/data \
  cloudreve:armv7

Notes

• Open http://<your server>:5212 and register the first account — it is automatically made the site administrator (Cloudreve v4 no longer prints a generated admin password to the logs like v3 did).
• TZ sets the container's timezone. Defaults to America/Toronto if not set.
• Aria2 is not required for normal Cloudreve file browsing, uploads, and downloads. Enable it only if you use Cloudreve's offline/remote download feature; build with INSTALL_ARIA2=1, run with CR_ENABLE_ARIA2=1, and publish 6888/tcp plus 6888/udp.
• To pin a specific Cloudreve version instead of the newest one, use an explicit tag, e.g. vedla/cloudreve:4.17.0.

Other guides

• If you want to use Nginx as a reverse proxy, see Cloudreve Docker - Nginx⁠.
• If you'd rather start the service with docker-compose, see Cloudreve Docker - Docker Compose⁠.
• If you want to run the service remotely in the cloud, see Cloudreve Docker - TeamCode⁠ (free usage time is limited per month; usage beyond that is billed).

⁠Upgrading

Stop and remove the running container, then pull the new image

docker stop cloudreve \
  && docker rm cloudreve \
  && docker pull vedla/cloudreve

Repeat the run steps above to start the container again.