Experimental owncloud image for docker
MIT License
Dockerfile
to create a Docker container image for ownCloud.
ownCloud is a self-hosted open source application for file hosting and sharing.
If you find this image useful here's how you can help:
Before reporting your issue please try updating Docker to the latest version and check if it resolves the issue. Refer to the Docker installation guide for instructions.
SELinux users should try disabling SELinux using the command setenforce 0
to see if it resolves the issue.
If the above recommendations do not help then report your issue along with the following information:
docker version
and docker info
commandsdocker run
command or docker-compose.yml
used to start the image. Mask out the sensitive bits.Automated builds of the image are available on Dockerhub and is the recommended method of installation.
Note: Builds are also available on Quay.io
docker pull sameersbn/owncloud:10.0.10-0
Alternatively you can build the image yourself.
docker build -t sameersbn/owncloud github.com/sameersbn/docker-owncloud
The quickest way to start using this image is with docker-compose.
wget https://raw.githubusercontent.com/sameersbn/docker-owncloud/master/docker-compose.yml
Update the OWNCLOUD_URL
environment variable in the docker-compose.yml
file with the url from which ownCloud will be externally accessible.
docker-compose up
Alternatively, you can start ownCloud manually using the Docker command line.
Step 1. Launch a PostgreSQL container
docker run --name owncloud-postgresql -itd --restart=always \
--env 'DB_NAME=owncloud_db' \
--env 'DB_USER=owncloud' --env 'DB_PASS=password' \
--volume /srv/docker/owncloud/postgresql:/var/lib/postgresql \
sameersbn/postgresql:9.6-4
Step 2. Launch the ownCloud php-fpm container
docker run --name owncloud -itd --restart=always \
--env OWNCLOUD_URL=http://cloud.example.com:10080 \
--link owncloud-postgresql:postgresql \
--volume /srv/docker/owncloud/owncloud:/var/lib/owncloud \
sameersbn/owncloud:10.0.10-0 app:owncloud
Step 3. Launch a NGINX frontend container
docker run --name owncloud-nginx -itd --restart=always \
--link owncloud:php-fpm \
--publish 10080:80 \
sameersbn/owncloud:10.0.10-0 app:nginx
Point your browser to http://cloud.example.com:10080
and login using the default username and password:
Note
Use the
OWNCLOUD_ADMIN_USER
andOWNCLOUD_ADMIN_PASSWORD
variables to create a custom admin user and password on the firstrun instead of the default credentials.
For ownCloud to preserve its state across container shutdown and startup you should mount a volume at /var/lib/owncloud
.
The Quickstart command already mounts a volume for persistence.
SELinux users should update the security context of the host mountpoint so that it plays nicely with Docker:
mkdir -p /srv/docker/owncloud
chcon -Rt svirt_sandbox_file_t /srv/docker/owncloud
The image allows users to create backups of the ownCloud installation using the app:backup:create
command or the owncloud-backup-create
helper script. The generated backup consists of configuration files, uploaded files and the sql database.
Before generating a backup — stop and remove the running instance.
docker stop owncloud && docker rm owncloud
Relaunch the container with the app:backup:create
argument.
docker run --name owncloud -it --rm [OPTIONS] \
sameersbn/owncloud:10.0.10-0 app:backup:create
The backup will be created in the backups/
folder of the Persistent volume. You can change the location using the OWNCLOUD_BACKUPS_DIR
configuration parameter.
NOTE
Backups can also be generated on a running instance using:
docker exec -it owncloud owncloud-backup-create
By default backups are held indefinitely. Using the OWNCLOUD_BACKUPS_EXPIRY
parameter you can configure how long (in seconds) you wish to keep the backups. For example, setting OWNCLOUD_BACKUPS_EXPIRY=604800
will remove backups that are older than 7 days. Old backups are only removed when creating a new backup, never automatically.
Backups created using instructions from the Creating backups section can be restored using the app:backup:restore
argument.
Before restoring a backup — stop and remove the running instance.
docker stop owncloud && docker rm owncloud
Relaunch the container with the app:backup:restore
argument. Ensure you launch the container in the interactive mode -it
.
docker run --name owncloud -it --rm [OPTIONS] \
sameersbn/owncloud:10.0.10-0 app:backup:restore
A list of existing backups will be displayed. Select a backup you wish to restore.
To avoid this interaction you can specify the backup filename using the BACKUP
argument to app:backup:restore
, eg.
docker run --name owncloud -it --rm [OPTIONS] \
sameersbn/owncloud:10.0.10-0 app:backup:restore BACKUP=1417624827_owncloud_backup.tar
To upgrade to newer releases:
docker pull sameersbn/owncloud:10.0.10-0
docker stop owncloud
docker rm -v owncloud
docker run -name owncloud -itd \
[OPTIONS] \
sameersbn/owncloud:10.0.10-0
For debugging and maintenance purposes you may want access the containers shell. If you are using Docker version 1.3.0
or higher you can access a running containers shell by starting bash
using docker exec
:
docker exec -it owncloud bash