Portainer Templates logo

Portainer Templates

Nextcloud (swarm) Nextcloud (swarm)

CloudProductivityToolsOtherWeb

Where are your photos and documents? With Nextcloud you pick a server of your choice, at home, in a data center or at a provider. And that is where your files will be. Nextcloud runs on that server, protecting your data and giving you access from your desktop or mobile devices.

Configuration

Type
Swarm
Platform
linux
Env vars
PUID=1000PGID=100TZ=''DATABASE_PASSWORD=''MYSQL_ROOT_PASSWORD=''PORT=''
Source
Repo

Template by mikestraney·Source

Notes

The database user is nextcloud and the database is nextcloud_db. The host of the database will be located at the bottom of the DB conotainer in portainer.

Services

nextcloud

Configuration

Image
nextcloud
Volumes
/var/www/html : nextcloud_data
Env vars
MYSQL_DATABASE=nextcloud_dbMYSQL_USER=nextcloudMYSQL_PASSWORD=mypassword
Restart
unless-stopped

Image details

Pulls: 1.0B
User: library
Created: Dec 30, 2016
Updated: 1 day ago
Status: active

nextcloud_db

Configuration

Image
mariadb
Volumes
/var/lib/mysql : nextcloud_db
Env vars
MYSQL_ROOT_PASSWORD=myrpasswordMYSQL_DATABASE=nextcloud_dbMYSQL_USER=nextcloudMYSQL_PASSWORD=mypassword
Restart
unless-stopped

Image details

Pulls: 3.2B
User: stackbrew
Created: Nov 25, 2014
Updated: 2 days ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying Nextcloud (swarm)

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Nextcloud (swarm), fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The swarm stack file this template deploys, straight from its repo:

version: '3.6'
services:
  nextcloud:
    image: nextcloud
    container_name: nextcloud
    environment:
      - MYSQL_DATABASE=nextcloud_db
      - MYSQL_USER=nextcloud
      - MYSQL_PASSWORD=mypassword
    volumes:
      - nextcloud_data:/var/www/html 
#    ports:
#      - ${PORT}:80
#      - ${PORT}:443
    restart: unless-stopped
#    depends_on:
#      - nextcloud_db
  nextcloud_db:
    image: mariadb
    container_name: nextcloud_db
    environment:
      - MYSQL_ROOT_PASSWORD=myrpassword
      - MYSQL_DATABASE=nextcloud_db
      - MYSQL_USER=nextcloud
      - MYSQL_PASSWORD=mypassword
    volumes:
      - nextcloud_db:/var/lib/mysql
    restart: unless-stopped

volumes:
  nextcloud_data:
  nextcloud_db:

Or deploy it directly from the source:

git clone https://github.com/mikestraney/portainer-templates
cd portainer-templates
docker stack deploy -c stacks/nextcloud/docker-stack.yml nextcloud-swarm

More install options in our documentation.

Container Documentation

nextcloud Documentation

Nextcloud manual docker image

nextcloud_db Documentation

MariaDB Server is a high performing open source relational database, forked from MySQL.

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Image won't pull

Test the pull directly on the host: docker pull nextcloud

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Swarm stack

Nextcloud (swarm) is a Swarm stack. Swarm is Docker's own way of running apps across more than one machine, so Portainer can spread it over a cluster and move it elsewhere if a server drops out.

The services

This stack is built from 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • nextcloud runs nextcloud
  • nextcloud_db runs mariadb

Volumes

A volume is where Nextcloud (swarm) keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/www/html kept in the nextcloud_data volume Docker manages
  • /var/lib/mysql kept in the nextcloud_db volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Nextcloud (swarm) takes 4 of them, all with defaults you can leave alone or tweak:

  • MYSQL_DATABASE, defaults to nextcloud_db
  • MYSQL_USER, defaults to nextcloud
  • MYSQL_PASSWORD, defaults to mypassword
  • MYSQL_ROOT_PASSWORD, defaults to myrpassword

Restart policy

The restart policy here is unless-stopped, so Docker restarts Nextcloud (swarm) after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like nextcloud) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Nextcloud (swarm) up. Add the template list to Portainer once, then deploying Nextcloud (swarm) is a click rather than a wall of config.