ownCloud docker with ownCloud X (10.8) as initial install.
100K+
OwnCloud provides universal access to your files via the web, your computer or your mobile devices wherever you are. Mariadb is built into the image. Built with php 7.2, 7.3, and 7.4, mariadb 10.3 and nginx 1.15. Owncloud.
docker create \
--name=ownCloud \
-p 443:443 \
-v <path to config>:/config \
-v <path to data>:/data \
-e PGID=<gid> \
-e PUID=<uid> \
-e TZ=<timezone> \
-e DB_PASS=<password> \
--privileged \
owncloud
The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side. For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container. So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.
-p 433 - the port(s)-v /config - path to ownCloud config files and database-v /data - path for ownCloud to store data-e PGID for GroupID - see below for explanation-e PUID for UserID - see below for explanation-e TZ timezone information -eg Europe/London-e DB_PASS ownCloud database password - see below for explanationIt is based on phusion baseimage with ssh removed, for shell access whilst the container is running do docker exec -it ownCloud /bin/bash.
Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.
In this instance PUID=1001 and PGID=1001. To find yours use id user as below:
$ id <dockeruser>
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
docker exec -it ownCloud /bin/bashdocker logs -f ownCloudContent type
Image
Digest
sha256:7f158128f…
Size
442.2 MB
Last updated
9 days ago
docker pull dlandon/owncloud