Bitnami Docker Image for ownCloud
Switch branches/tags
10.0.10-ol-7-r5 10.0.10-ol-7-r4 10.0.10-ol-7-r3 10.0.10-ol-7-r2 10.0.10-ol-7-r1 10.0.10-ol-7-r0 10.0.10-debian-9-r5 10.0.10-debian-9-r4 10.0.10-debian-9-r3 10.0.10-debian-9-r2 10.0.10-debian-9-r1 10.0.10-debian-9-r0 10.0.9-ol-7-r49 10.0.9-ol-7-r48 10.0.9-ol-7-r47 10.0.9-ol-7-r46 10.0.9-ol-7-r45 10.0.9-ol-7-r44 10.0.9-ol-7-r43 10.0.9-ol-7-r42 10.0.9-ol-7-r41 10.0.9-ol-7-r40 10.0.9-ol-7-r39 10.0.9-ol-7-r38 10.0.9-ol-7-r37 10.0.9-ol-7-r36 10.0.9-ol-7-r35 10.0.9-ol-7-r34 10.0.9-ol-7-r33 10.0.9-ol-7-r32 10.0.9-ol-7-r31 10.0.9-ol-7-r30 10.0.9-ol-7-r29 10.0.9-ol-7-r28 10.0.9-ol-7-r27 10.0.9-ol-7-r26 10.0.9-ol-7-r25 10.0.9-ol-7-r24 10.0.9-ol-7-r23 10.0.9-ol-7-r22 10.0.9-ol-7-r21 10.0.9-ol-7-r20 10.0.9-ol-7-r19 10.0.9-ol-7-r18 10.0.9-ol-7-r17 10.0.9-ol-7-r16 10.0.9-ol-7-r15 10.0.9-ol-7-r14 10.0.9-ol-7-r13 10.0.9-ol-7-r12 10.0.9-ol-7-r11 10.0.9-ol-7-r10 10.0.9-ol-7-r9 10.0.9-ol-7-r8 10.0.9-ol-7-r7 10.0.9-ol-7-r6 10.0.9-ol-7-r5 10.0.9-ol-7-r4 10.0.9-ol-7-r3 10.0.9-ol-7-r2 10.0.9-ol-7-r1 10.0.9-ol-7-r0 10.0.9-debian-9-r46 10.0.9-debian-9-r45 10.0.9-debian-9-r44 10.0.9-debian-9-r43 10.0.9-debian-9-r42 10.0.9-debian-9-r41 10.0.9-debian-9-r40 10.0.9-debian-9-r39 10.0.9-debian-9-r38 10.0.9-debian-9-r37 10.0.9-debian-9-r36 10.0.9-debian-9-r35 10.0.9-debian-9-r34 10.0.9-debian-9-r33 10.0.9-debian-9-r32 10.0.9-debian-9-r31 10.0.9-debian-9-r30 10.0.9-debian-9-r29 10.0.9-debian-9-r28 10.0.9-debian-9-r27 10.0.9-debian-9-r26 10.0.9-debian-9-r25 10.0.9-debian-9-r24 10.0.9-debian-9-r23 10.0.9-debian-9-r22 10.0.9-debian-9-r21 10.0.9-debian-9-r20 10.0.9-debian-9-r19 10.0.9-debian-9-r18 10.0.9-debian-9-r17 10.0.9-debian-9-r16 10.0.9-debian-9-r15 10.0.9-debian-9-r14 10.0.9-debian-9-r13 10.0.9-debian-9-r12 10.0.9-debian-9-r11 10.0.9-debian-9-r10 10.0.9-debian-9-r9
Nothing to show
Clone or download

README.md

CircleCI

What is ownCloud?

ownCloud is a file sharing server that puts the control and security of your own data back into your hands.

https://owncloud.org/

TL;DR;

Docker Compose

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-owncloud/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

Why use Bitnami Images?

  • Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
  • With Bitnami images the latest bug fixes and features are available as soon as possible.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • Bitnami images are built on CircleCI and automatically pushed to the Docker Hub.
  • All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.

How to deploy ownCloud in Kubernetes?

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami ownCloud Chart GitHub repository.

Supported tags and respective Dockerfile links

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

Subscribe to project updates by watching the bitnami/owncloud GitHub repo.

Prerequisites

To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.

Run ownCloud with a Database Container

Running ownCloud with a database server is the recommended way. You can either use docker-compose or run the containers manually.

Run the application using Docker Compose

This is the recommended way to run ownCloud. You can use the following docker compose template:

version: '2'
services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - MARIADB_USER=bn_owncloud
      - MARIADB_DATABASE=bitnami_owncloud
    volumes:
      - 'mariadb_data:/bitnami'
  owncloud:
    image: 'bitnami/owncloud:latest'
    environment:
      - MARIADB_HOST=mariadb
      - MARIADB_PORT_NUMBER=3306
      - OWNCLOUD_DATABASE_USER=bn_owncloud
      - OWNCLOUD_DATABASE_NAME=bitnami_owncloud
      - ALLOW_EMPTY_PASSWORD=yes
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - 'owncloud_data:/bitnami'
    depends_on:
      - mariadb
volumes:
  mariadb_data:
    driver: local
  owncloud_data:
    driver: local

Run the application manually

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

  1. Create a new network for the application and the database:
$ docker network create owncloud-tier
  1. Create a volume for MariaDB persistence and create a MariaDB container
$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e MARIADB_USER=bn_owncloud \
  -e MARIADB_DATABASE=bitnami_owncloud \
  --net owncloud-tier \
  --volume mariadb_data:/bitnami \
  bitnami/mariadb:latest

Note: You need to give the container a name in order to OwnCloud to resolve the host

  1. Create volumes for Owncloud persistence and launch the container
$ docker volume create --name owncloud_data
$ docker run -d --name owncloud -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e OWNCLOUD_DATABASE_USER=bn_owncloud \
  -e OWNCLOUD_DATABASE_NAME=bitnami_owncloud \
  --net owncloud-tier \
  --volume owncloud_data:/bitnami \
  bitnami/owncloud:latest

Then you can access your application at http://your-ip/

Note: If you want to access your application from a public IP or hostname you need to configure as a Trusted Domain. You can handle it adjusting the configuration of the instance by setting the environment variable "OWNCLOUD_HOST" to your public IP or hostname.

Note: If you persisted your application and you already run your container, you won't be able to configure the Trusted Domains using the previous environment variable. Trusted Domains will be set using the configuration that had been previously persisted. Therefore, you will need to connect you container and execute the command below:

$ sudo -u daemon /opt/bitnami/php/bin/php /opt/bitnami/owncloud/occ config:system:set trusted_domains 2 --value=YOUR_HOSTNAME

Persisting your application

If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a volume at the /bitnami path. Additionally you should mount a volume for persistence of the MariaDB data.

The above examples define docker volumes namely mariadb_data and owncloud_data. The ownCloud application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Mount persistent folders in the host using docker-compose

This requires a minor change to the docker-compose.yml template previously shown:

version: '2'

services:
  mariadb:
    image: 'bitnami/mariadb:latest'
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - MARIADB_USER=bn_owncloud
      - MARIADB_DATABASE=bitnami_owncloud
    volumes:
      - '/path/to/mariadb-persistence:/bitnami'
  owncloud:
    image: 'bitnami/owncloud:latest'
    environment:
      - OWNCLOUD_DATABASE_USER=bn_owncloud
      - OWNCLOUD_DATABASE_NAME=bitnami_owncloud
      - ALLOW_EMPTY_PASSWORD=yes
    depends_on:
      - mariadb
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - '/path/to/owncloud-persistence:/bitnami'

Mount host directories as data volumes using the Docker command line

In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:

  1. Create a network (if it does not exist):
$ docker network create owncloud-tier
  1. Create a MariaDB container with host volume:
$ docker run -d --name mariadb \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e MARIADB_USER=bn_owncloud \
  -e MARIADB_DATABASE=bitnami_owncloud \
  --net owncloud-tier \
  --volume /path/to/mariadb-persistence:/bitnami \
  bitnami/mariadb:latest

Note: You need to give the container a name in order to OwnCloud to resolve the host

  1. Create the ownCloud container with host volumes:
$ docker run -d --name owncloud -p 80:80 -p 443:443 \
  -e ALLOW_EMPTY_PASSWORD=yes \
  -e OWNCLOUD_DATABASE_USER=bn_owncloud \
  -e OWNCLOUD_DATABASE_NAME=bitnami_owncloud \
  --net owncloud-tier \
  --volume /path/to/owncloud-persistence:/bitnami \
  bitnami/owncloud:latest

Upgrade this application

Bitnami provides up-to-date versions of MariaDB and OwnCloud, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the OwnCloud container. For the MariaDB upgrade see https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image

  1. Get the updated images:
$ docker pull bitnami/owncloud:latest
  1. Stop your container
  • For docker-compose: $ docker-compose stop owncloud
  • For manual execution: $ docker stop owncloud
  1. Take a snapshot of the application state
$ rsync -a /path/to/owncloud-persistence /path/to/owncloud-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the MariaDB data

You can use these snapshots to restore the application state should the upgrade fail.

  1. Remove the currently running container
  • For docker-compose: $ docker-compose rm -v owncloud
  • For manual execution: $ docker rm -v owncloud
  1. Run the new image
  • For docker-compose: $ docker-compose up owncloud
  • For manual execution (mount the directories if needed): docker run --name owncloud bitnami/owncloud:latest

Configuration

Environment variables

When you start the owncloud image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line.

User and Site configuration
  • APACHE_HTTP_PORT_NUMBER: Port used by Apache for HTTP. Default: 80
  • APACHE_HTTPS_PORT_NUMBER: Port used by Apache for HTTPS. Default: 443
  • OWNCLOUD_USERNAME: Owncloud application username. Default: user
  • OWNCLOUD_PASSWORD: Owncloud application password. Default: bitnami
  • OWNCLOUD_EMAIL: Owncloud application email. Default: user@example.com
  • OWNCLOUD_WEB_SERVER_HOST: Owncloud Host Server.
Use an existing database
  • MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
  • MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
  • OWNCLOUD_DATABASE_NAME: Database name that ownCloud will use to connect with the database. Default: bitnami_owncloud
  • OWNCLOUD_DATABASE_USER: Database user that ownCloud will use to connect with the database. Default: bn_owncloud
  • OWNCLOUD_DATABASE_PASSWORD: Database password that ownCloud will use to connect with the database. No defaults.
  • ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no
Create a database for ownCloud using mysql-client
  • MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
  • MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306
  • MARIADB_ROOT_USER: Database admin user. Default: root
  • MARIADB_ROOT_PASSWORD: Database password for the MARIADB_ROOT_USER user. No defaults.
  • MYSQL_CLIENT_CREATE_DATABASE_NAME: New database to be created by the mysql client module. No defaults.
  • MYSQL_CLIENT_CREATE_DATABASE_USER: New database user to be created by the mysql client module. No defaults.
  • MYSQL_CLIENT_CREATE_DATABASE_PASSWORD: Database password for the MYSQL_CLIENT_CREATE_DATABASE_USER user. No defaults.
  • ALLOW_EMPTY_PASSWORD: It can be used to allow blank passwords. Default: no

If you want to add a new environment variable:

  • For docker-compose add the variable name and value under the application section:
owncloud:
  image: bitnami/owncloud:latest
  ports:
    - 80:80
    - 443:443
  environment:
    - OWNCLOUD_HOST=your_host
  volumes:
      - owncloud_data:/bitnami
  • For manual execution add a -e option with each variable and value:
$ docker run -d --name owncloud -p 80:80 -p 443:443 \
  -e OWNCLOUD_PASSWORD=my_password \
  --net owncloud-tier \
  --volume /path/to/owncloud-persistence:/bitnami \
  bitnami/owncloud:latest

Contributing

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

Issues

  • Host OS and version
  • Docker version (docker version)
  • Output of docker info
  • Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
  • The command you used to run the container, and any relevant output you saw (masking any sensitive information)

License

Copyright 2016-2018 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.