Public | Automated Build

Last pushed: 3 months ago
Short Description
Bitnami Docker Image for Owncloud
Full Description

What is ownCloud?

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


Docker Compose

$ curl -sSL > docker-compose.yml
$ docker-compose up -d


WARNING: This is a beta configuration, currently unsupported.

Get the raw URL pointing to the kubernetes.yml manifest and use kubectl to create the resources on your Kubernetes cluster like so:

$ kubectl create -f

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.


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'
    image: 'bitnami/mariadb:latest'
      - 'mariadb_data:/bitnami'
    image: 'bitnami/owncloud:latest'
      - '80:80'
      - '443:443'
      - 'owncloud_data:/bitnami'
      - mariadb
    driver: local
    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
  2. Start a MariaDB database in the network generated:

    $ docker run -d --name mariadb -e ALLOW_EMPTY_PASSWORD=yes --net=owncloud-tier bitnami/mariadb

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

  3. Run the OwnCloud container:

    $ docker run -d -p 80:80 --name owncloud --net=owncloud-tier bitnami/owncloud

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'

    image: 'bitnami/mariadb:latest'
      - '/path/to/mariadb-persistence:/bitnami'
    image: 'bitnami/owncloud:latest'
      - mariadb
      - '80:80'
      - '443:443'
      - '/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
  2. Create a MariaDB container with host volume:

    $ docker run -d --name mariadb -e ALLOW_EMPTY_PASSWORD=yes \
     --net owncloud-tier \
     --volume /path/to/mariadb-persistence:/bitnami \

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

  3. Create the ownCloud container with host volumes:

    $ docker run -d --name owncloud -p 80:80 -p 443:443 \
     --net owncloud-tier \
     --volume /path/to/owncloud-persistence:/bitnami \

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

  1. Get the updated images:

    $ docker pull bitnami/owncloud:latest
  2. Stop your container

    • For docker-compose: $ docker-compose stop owncloud
    • For manual execution: $ docker stop owncloud
  3. 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
  2. Run the new image

    • For docker-compose: $ docker-compose start owncloud
    • For manual execution (mount the directories if needed): docker run --name owncloud bitnami/owncloud:latest


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. If you want to add a new environment variable:

  • For docker-compose add the variable name and value under the application section:
  image: bitnami/owncloud:latest
    - 80:80
    - 443:443
    - OWNCLOUD_HOST=your_host
      - 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 \

Available variables:

  • 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:
  • OWNCLOUD_WEB_SERVER_HOST: Owncloud Host Server.
  • MARIADB_PASSWORD: Root password for the MariaDB.
  • MARIADB_HOST: Hostname for MariaDB server. Default: mariadb
  • MARIADB_PORT_NUMBER: Port used by MariaDB server. Default: 3306


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.


If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

  • 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)


Most real time communication happens in the #containers channel at; you can sign up at

Discussions are archived at


Copyright 2016-2017 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

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Docker Pull Command
Source Repository