Public | Automated Build

Last pushed: 6 months ago
Short Description
Dockerized OwnCloud based on alpine.
Full Description

#OwnCloud with Docker
Based on lgreyltc/docker-archlinux

Table of Contents


  • Full owncloud instance
  • OneClick/Run installation
  • Enforced ssl encryption
  • Backup cronjobs

Get the image:

docker pull martingabelmann/owncloud

It is highly recommended to use owncloud with ssl, so the apache-settings are forcing the browser to use https://. There are certificates build in the image for testing but in production you`ll have to use your own:

Assuming you owning (trusted) ssl-certificates at

  • /srv/docker/owncloud/ssl/server.key and
  • /srv/docker/owncloud/ssl/server.crt,

that are beloging to the domain,

choose a good database- and adminpassword, then type:

docker run --name=oc -d -p 443:443 -p 80:80 \
  -e DB_PASS=changemepls -e OC_ADMINPASS=changemepls \
  -e -e \
  -v /srv/docker/owncloud/data/:/srv/http/data/ \
  -v /srv/docker/owncloud/config/:/srv/http/config/ \
  -v /srv/docker/owncloud/apps/:/srv/http/apps2/ \
  -v /srv/docker/owncloud/sql/:/var/lib/postgres/data/ \
  -v /srv/docker/owncloud/ssl/:/ssl/ martingabelmann/owncloud

This will mount and use the certificates. Your {data,config,additional apps} are stored on your host at /srv/docker/owncloud/{data,config,apps} and the postgres database at /srv/docker/owncloud/sql.

The first run will take a while because the recent owncloud-version will be downloaded and exctracted.

Check docker logs oc to verify that everything is done. Then point your browser to On the first vistit/install Owncloud will do some configurations and directly login into to the admin panel.

The image provides a script called backup which is used to tar the data, config, apps and sql directories into OC_BACKUP_DIR and extract existing tarfiles from there into the corresponig destinations.


  • You can either join the containers bash with a

    docker exec -ti oc bash

    and run the backup [options]-command from there or run it directly from the host:

    docker exec -ti oc backup [options]
  • To perform a new backup run backup -b. The file is placed into data/backups and called like owncloud_yearmonthday_time.tar.gz. Depending on the variable OC_BACKUP_FILES (default=1), old backupfiles will be deleted.

The installscript is able to set a cronjob with that backup script. Because some people may have less storage it is disabled by default. To enable it just set the OC_BACKUP_CRON variable with the usual cron shurtcuts (see here, e.g. to do a daily backup at midnight use
-e OC_BACKUP_CRON='@midnight').

Full example to store the last 2 backups done at every midnight:

docker run --name=oc -d -p 443:443 -p 80:80 \
  -e DB_PASS=changemepls -e OC_ADMINPASS=changemepls \
  -e -e \
  -e OC_BACKUP_CRON='@midnight' \
  -v /srv/docker/owncloud/data/:/srv/http/data/ \
  -v /srv/docker/owncloud/config/:/srv/http/config/ \
  -v /srv/docker/owncloud/apps/:/srv/http/apps2/ \
  -v /srv/docker/owncloud/sql/:/var/lib/postgres/data/ \
  -v /srv/docker/owncloud/ssl/:/ssl/ martingabelmann/owncloud


  • Get a list of all available backups with backup -l,
  • copy the filename of your choise (including extension),
  • restore with backup -r filename.tar.gz

However I can not give full warranty that restoring backups will work in every situation! It passed my daily usage but in some special configurations you may have to use a external backup service.


A minimal working owncloud instance can be run with

docker run --name=octest -d -p 44300:443 -p 8000:80 martingabelmann/owncloud

Then point your browser to https://localhost:44300. The container will use the build-in certificates, so be carefully, dont use this in public networks/production!

Debuginformations can be viewed with
docker logs oc
or from inside the container (docker exec -ti oc) under /var/log/ about apache, postgresql, cron and backups.

Owncloud cli

OwnCloud offers the possibility to do administrative tasks via the command line interface occ. Just try it

docker exec oc occ help


Because the install script is downloading the newest stable version, updates can be easily done by removing the running container and starting a new one. Since the apps arent effected they will be upgraded by the webinterface on the next visit or via the command line.

I recommend to upgrade via occ:

docker exec oc occ upgrade

Sometimes it happens that a upgrade fails and breaks your OwnCloud webinterface because a app isnt compatible (or so). Then you have to disable the app with

docker exec oc occ app:disable APPNAME

you may ask which apps are broken. Find out by observing /srv/http/data/owncloud.log`. Check a specific app with

docker exec oc app:check APPNAME

for compatiblity. If it fails, install the newest/compatible version by copying into /srv/data/apps/ (e.g. pulling from github). Afterwards try to enable it

docker exec oc app:enable APPNAME

If everything was successful you should be able to visit the webinterface again.

Docker Pull Command
Source Repository