docker-owncloud

This repository is deprecated. Please use something else which is still maintained.

Maintainer wanted. Refer to #62

Docker image for ownCloud.

The build instructions are tracked on GitHub. Automated builds are hosted on Docker Hub.

Why using this image

• It is directly based on Debian stable. No additional image layers which blow up the total image size and might by a security risk.
• Uses nginx as webserver.
• Hardened TLS configuration.
• Generates unique Diffie Hellman parameters to mitigate precomputation based attacks on common parameters. Refs: Guide to Deploying Diffie-Hellman for TLS.
• Local caching enabled by default (APCu). See https://owncloud.org/blog/making-owncloud-faster-through-caching/
• Installs the ownCloud tarball directly from https://owncloud.org/ and it securely verifies the GPG signature.
• Makes installing of 3party apps easy and keeps them across updates.
• The occ command can be used just by typing docker exec -ti $owncloud_container_name occ.
• ownCloud can only be updated by redeploying the container. No update via the web interface is possible. The ownCloud installation is fully contained in the container and not made persistent. This allows to make the ownCloud installation write protected for the Webserver and PHP which run as www-data.
• Automated database update on ownCloud update during the startup of a redeployed/updated container.

Getting the image

You have two options to get the image:

1. Build it yourself with make build.
2. Download it via docker pull jchaney/owncloud (automated build).

ownCloud up and running

Checkout the Makefile for an example or just run make owncloud which will setup a ownCloud container instance (called "owncloud"). After that, just head over to http://localhost/ and give it a try. You can now create an admin account. For testing purposes you can use SQLite (but remember to use a real database in production).

Running ownCloud in production

Setup a separate container running your database server and link it to the ownCloud container. For running in production, you need to provide a TLS key and certificate. The Makefile defaults to /etc/ssl/private/ssl-cert-snakeoil.key and /etc/ssl/certs/ssl-cert-snakeoil.pem. Make sure those files exist or extend the Makefile (you can include this Makefile and overwrite some variables in your own Makefile). You might also want to change variables like docker_owncloud_permanent_storage to define where the persistent data will be stored. To generate self signed once you can run the following command:

make-ssl-cert generate-default-snakeoil

To setup ownCloud with MariaDB as backend, just run:

make owncloud-production

In the initial ownCloud setup, you need to supply the database user, password, database name and database host which you can look up via:

make owncloud-mariadb-get-pw

Note that this command also shows you the MariaDB root password which you need to write down because you will not be able to access it later (after you run make owncloud-production again to update the containers, the passwords will be different and not match the once which are actually used).

That should be it 😄

Update your container and ownCloud

It is recommended to rebuild/pull this image on a regular basis and redeploy your ownCloud container(s) to get the latest security fixes. Note that ownCloud version jumps are uploaded to the latest tag of this image once they are tested. You might want to watch this repository to see when this happens.

Once the ownCloud image is up-to-date, just run:

make owncloud-production

to update your container. ownCloud usually requires a database update when the version of ownCloud is bumped. This process has been automated for this Docker image but remember that you are still in charge of making backups/snapshots prior to updates!

Installing 3party apps

Just write the command(s) needed to install apps in a configuration file and make sure it is present as /owncloud/3party_apps.conf in your container.

Checkout the example configuration and the install script for details.

docker-compose support

You can also run this image with docker-compose. First you need to declare all env variables since docker-compose does not support (yet) default variables.

# Where to store data and database ?
export docker_owncloud_permanent_storage="~/owncloud_data"

# SSL Certificates to use.
export docker_owncloud_ssl_cert="../certs/cloud.cert"
export docker_owncloud_ssl_key="../certs/cloud.key"

# Servername
export docker_owncloud_servername="localhost"

export docker_owncloud_http_port="80"
export docker_owncloud_https_port="443"
export docker_owncloud_in_root_path="1"

export docker_owncloud_mariadb_root_password=$(pwgen --secure 40 1)
export docker_owncloud_mariadb_user_password=$(pwgen --secure 40 1)

export image_owncloud="jchaney/owncloud"
export image_mariadb="mysql"

Then:

docker-compose up

That's all !

Related projects

• official docker repository for ownCloud

  Uses Apache as webserver and is based on the official Docker PHP image.

• l3iggs/owncloud

  Uses Apache as webserver and is based on a self build LAMP stack based on Arch Linux.

• Ansible role to install and manage ownCloud instances

  Automation framework for setting up ownCloud on any Debian based system. This offers much more flexibility and is not limited to Docker. So you can setup a ownCloud instance in a KVM virtual machine and/or a LXC container for example.

  This role is part of the DebOps project which allows you to automate all the steps mentioned above (setting up a Hypervisor host with support for KVM and/or LXC, setting up the virtual machine/container and installing Webserver/PHP/Database and finally ownCloud).

  The real fun with this approach begins when you manage multiple instances because Ansible and this role allow you to run actions like ownCloud updates or enabling apps or the like on all your instances automatically.

Maintainer

The current maintainer is Robin ypid Schneider.

List of previous maintainers:

1. Josh Chaney
2. silvio

Problems

• If you get "Command not found" for any of the programs used then install it (make sure you know what you are doing).

  Your distribution packages: You should find missing dependencies from the errors yourself. It's your machine, you're supposed to know it.

  Ref: https://bb.osmocom.org/trac/wiki/PreliminaryRequirements#Generalknowledge

License

This project is distributed under GNU Affero General Public License, Version 3.