Public | Automated Build

Last pushed: 10 months ago
Short Description
Dockerized Nextcloud
Full Description

sameersbn/nextcloud:11.0.1

Introduction

Dockerfile to create a Docker container image for Nextcloud.

Nextcloud is a self-hosted open source application for file hosting and sharing.

Contributing

If you find this image useful here's how you can help:

  • Send a pull request with your awesome features and bug fixes
  • Help users resolve their issues.
  • Support the development of this image with a donation

Issues

Before reporting your issue please try updating Docker to the latest version and check if it resolves the issue. Refer to the Docker installation guide for instructions.

SELinux users should try disabling SELinux using the command setenforce 0 to see if it resolves the issue.

If the above recommendations do not help then report your issue along with the following information:

  • Output of the docker version and docker info commands
  • The docker run command or docker-compose.yml used to start the image. Mask out the sensitive bits.
  • Please state if you are using Boot2Docker, VirtualBox, etc.

Getting started

Installation

Automated builds of the image are available on Dockerhub and is the recommended method of installation.

Note: Builds are also available on Quay.io

docker pull sameersbn/nextcloud:11.0.1

Alternatively you can build the image yourself.

docker build -t sameersbn/nextcloud github.com/sameersbn/docker-nextcloud

Quickstart

The quickest way to start using this image is with docker-compose.

wget https://raw.githubusercontent.com/sameersbn/docker-nextcloud/master/docker-compose.yml

Update the NEXTCLOUD_URL environment variable in the docker-compose.yml file with the url from which Nextcloud will be externally accessible.

docker-compose up

Alternatively, you can start Nextcloud manually using the Docker command line.

Step 1. Launch a PostgreSQL container

docker run --name nextcloud-postgresql -itd --restart=always \
  --env 'DB_NAME=nextcloud_db' \
  --env 'DB_USER=nextcloud' --env 'DB_PASS=password' \
  --volume /srv/docker/nextcloud/postgresql:/var/lib/postgresql \
  sameersbn/postgresql:9.6-2

Step 2. Launch the Nextcloud php-fpm container

docker run --name nextcloud -itd --restart=always \
  --env NEXTCLOUD_URL=http://cloud.example.com:10080 \
  --link nextcloud-postgresql:postgresql \
  --volume /srv/docker/nextcloud/nextcloud:/var/lib/nextcloud \
  sameersbn/nextcloud:11.0.1 app:nextcloud

Step 3. Launch a NGINX frontend container

docker run --name nextcloud-nginx -itd --restart=always \
  --link nextcloud:php-fpm \
  --publish 10080:80 \
  sameersbn/nextcloud:11.0.1 app:nginx

Point your browser to http://cloud.example.com:10080 and login using the default username and password:

  • username: admin
  • password: password

Note

Use the NEXTCLOUD_ADMIN_USER and NEXTCLOUD_ADMIN_PASSWORD variables to create a custom admin user and password on the firstrun instead of the default credentials.

Persistence

For Nextcloud to preserve its state across container shutdown and startup you should mount a volume at /var/lib/nextcloud.

The Quickstart command already mounts a volume for persistence.

SELinux users should update the security context of the host mountpoint so that it plays nicely with Docker:

mkdir -p /srv/docker/nextcloud
chcon -Rt svirt_sandbox_file_t /srv/docker/nextcloud

Maintenance

Creating backups

The image allows users to create backups of the Nextcloud installation using the app:backup:create command or the nextcloud-backup-create helper script. The generated backup consists of configuration files, uploaded files and the sql database.

Before generating a backup — stop and remove the running instance.

docker stop nextcloud && docker rm nextcloud

Relaunch the container with the app:backup:create argument.

docker run --name nextcloud -it --rm [OPTIONS] \
  sameersbn/nextcloud:11.0.1 app:backup:create

The backup will be created in the backups/ folder of the Persistent volume. You can change the location using the NEXTCLOUD_BACKUPS_DIR configuration parameter.

NOTE

Backups can also be generated on a running instance using:

 docker exec -it nextcloud nextcloud-backup-create

By default backups are held indefinitely. Using the NEXTCLOUD_BACKUPS_EXPIRY parameter you can configure how long (in seconds) you wish to keep the backups. For example, setting NEXTCLOUD_BACKUPS_EXPIRY=604800 will remove backups that are older than 7 days. Old backups are only removed when creating a new backup, never automatically.

Restoring Backups

Backups created using instructions from the Creating backups section can be restored using the app:backup:restore argument.

Before restoring a backup — stop and remove the running instance.

docker stop nextcloud && docker rm nextcloud

Relaunch the container with the app:backup:restore argument. Ensure you launch the container in the interactive mode -it.

docker run --name nextcloud -it --rm [OPTIONS] \
  sameersbn/nextcloud:11.0.1 app:backup:restore

A list of existing backups will be displayed. Select a backup you wish to restore.

To avoid this interaction you can specify the backup filename using the BACKUP argument to app:backup:restore, eg.

docker run --name nextcloud -it --rm [OPTIONS] \
  sameersbn/nextcloud:11.0.1 app:backup:restore BACKUP=1417624827_nextcloud_backup.tar

Upgrading

To upgrade to newer releases:

  1. Download the updated Docker image:

    docker pull sameersbn/nextcloud:11.0.1
    
  2. Stop the currently running image:

    docker stop nextcloud
    
  3. Remove the stopped container

    docker rm -v nextcloud
    
  4. Start the updated image

    docker run -name nextcloud -itd \
    [OPTIONS] \
    sameersbn/nextcloud:11.0.1
    

Shell Access

For debugging and maintenance purposes you may want access the containers shell. If you are using Docker version 1.3.0 or higher you can access a running containers shell by starting bash using docker exec:

docker exec -it nextcloud bash
Docker Pull Command
Owner
sameersbn
Source Repository