10.0.2-apache
,10.0-apache
,10-apache
,apache
,10.0.2
,10.0
,10
,latest
(10.0/apache/Dockerfile)10.0.2-fpm
,10.0-fpm
,10-fpm
,fpm
(10.0/fpm/Dockerfile)9.1.6-apache
,9.1-apache
,9-apache
,9.1.6
,9.1
,9
(9.1/apache/Dockerfile)9.1.6-fpm
,9.1-fpm
,9-fpm
(9.1/fpm/Dockerfile)9.0.10-apache
,9.0-apache
,9.0.10
,9.0
(9.0/apache/Dockerfile)9.0.10-fpm
,9.0-fpm
(9.0/fpm/Dockerfile)
-
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow -
Where to file issues:
https://github.com/docker-library/owncloud/issues -
Maintained by:
the Docker Community -
Published image artifact details:
repo-info repo'srepos/owncloud/
directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images PRs with labellibrary/owncloud
official-images repo'slibrary/owncloud
file (history) -
Source of this description:
docs repo'sowncloud/
directory (history) -
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
ownCloud is a self-hosted file sync and share server. It provides access to your data through a web interface, sync clients or WebDAV while providing a platform to view, sync and share across devices easily—all under your control. ownCloud’s open architecture is extensible via a simple but powerful API for applications and plugins and it works with any storage.
Starting the ownCloud 8.1 instance listening on port 80 is as easy as the following:
$ docker run -d -p 80:80 owncloud:8.1
Then go to http://localhost/ and go through the wizard. By default this container uses SQLite for data storage, but the wizard should allow for connecting to an existing database. Additionally, tags for 6.0, 7.0, or 8.0 are available.
For a MySQL database you can link an database container, e.g. --link my-mysql:mysql
, and then use mysql
as the database host on setup.
All data beyond what lives in the database (file uploads, etc) is stored within the default volume /var/www/html
. With this volume, ownCloud will only be updated when the file version.php
is not present.
-v /<mydatalocation>:/var/www/html
For fine grained data persistence, you can use 3 volumes, as shown below.
-v /<mydatalocation>/apps:/var/www/html/apps
installed / modified apps-v /<mydatalocation>/config:/var/www/html/config
local configuration-v /<mydatalocation>/data:/var/www/html/data
the actual data of your ownCloud
When using the 6.0 image, you need to map the host port to the container port that apache listens on when going through the installation wizard. By default, this is port 80.
The occ
tool from upstream is simplest to use via docker exec
, similar to the example provided there:
$ docker exec -u www-data some-owncloud php occ status
... via docker stack deploy
or docker-compose
Example stack.yml
for owncloud
:
# ownCloud with MariaDB/MySQL
#
# Access via "http://localhost:8080" (or "http://$(docker-machine ip):8080" if using docker-machine)
#
# During initial ownCloud setup, select "Storage & database" --> "Configure the database" --> "MySQL/MariaDB"
# Database user: root
# Database password: example
# Database name: pick any name
# Database host: replace "localhost" with "mysql"
version: '3.1'
services:
owncloud:
image: owncloud
ports:
- 8080:80
mysql:
image: mariadb
environment:
MYSQL_ROOT_PASSWORD: example
Run docker stack deploy -c stack.yml owncloud
(or docker-compose -f stack.yml up
), wait for it to initialize completely, and visit http://swarm-ip:8080/
, http://localhost:8080/
, or http://host-ip:8080
(as appropriate).
View license information for the software contained in this image.