Public | Automated Build

Last pushed: a day ago
Short Description
Nextcloud: a safe home for all your data. Developed in an open, transparent and trustworthy way.
Full Description


This is just like my ownCloud server Docker container repo only it's for Nextcloud. Here is some background relating to the ownCloud/Nextcloud fissure.

Simple to use Docker container with the latest stable Nextcloud server release, complete with all the bells and whistles. This project is 100% transparent and trustable, every file in the resulting docker image is traceable and inspectable by following up the docker image depenancy tree which starts with my Arch Linux base image.

Please report any issues or improvement ideas to the github issue tracker
Pull requests welcome! Let's work together!

Say thanks by adding a star here and/or here.


  1. Install docker
  2. Download and start the Nextcloud server instance

    docker pull greyltc/nextcloud
    docker run --name nc -p 80:80 -p 443:443 -d greyltc/nextcloud
  3. Access your Nextcloud server
    Point your web browser to https://localhost/nextcloud
    Note: If you're on MacOS or Windows you can't use "localhost" here. Run docker-machine ip default to figure out what you should use in place of localhost.
  4. Setup nextcloud
    Follow the instructions in your browser to perform the initial setup of your server.

  5. [Optional] Stop the server instance

    docker stop nc

    You can restart the container later with docker start nc

  6. [Optional] Delete the server instance

    docker rm nc #<--WARNING: this will delete anything stored inside the container
  7. Profit.
Docker Pull Command
Source Repository

Comments (5)
a year ago

Is it possible to access the docker nextcloud from outside the local network e.g. access home from work.
Probably I should forward a port from the router/modem to the docker but then what else is needed?

a year ago

Anyone have any luck using Certbot certs with this?

a year ago

Hi, I'm trying but for some reason apache it not starting

[root@49198bae3d76 conf]# cat /usr/bin/start-servers

#!/usr/bin/env bash

if [ "$ENABLE_DAV" = true ] ; then
sed -i '$a Include conf/extra/httpd-dav.conf'
sed -i '|Include conf/extra/httpd-dav.conf|d' /etc/httpd/conf/httpd.conf

the systemd services generally create these folders, make them now manually

mkdir -p /run/httpd
mkdir -p /run/postgresql && chown postgres /run/postgresql

[ "$START_POSTGRESQL" = true ] && su postgres -c 'pg_ctl -s -D /var/lib/postgres/data start -w -t 120'
[ "$START_MYSQL" = true ] && cd /usr && /usr/bin/mysqld_safe --datadir=/var/lib/mysql&
[ "$DO_SSL_SELF_GENERATION" = true ] && setup-apache-ssl-key
[ "$START_APACHE" = true ] && apachectl start
[ "$DO_SSL_LETS_ENCRYPT_FETCH" = true ] && setup-apache-ssl-key
[ "$ENABLE_CRON" = true ] && crond
[root@49198bae3d76 conf]# setup-apache-ssl-key
[root@49198bae3d76 conf]# apachectl start
AH00526: Syntax error on line 165 of /etc/httpd/conf/extra/httpd-ssl.conf:
SSLCertificateChainFile: file '/root/sslKeys/server.chain' does not exist or is empty

a year ago

One question: can you tell me how I can install a certifcate so as to eliminate the HTTPS: privacy warnings when remote-connected? Is that possible?

a year ago


You have helped me do something I have tried (and failed) to do for many many hours. I now have my own https: remote-accessible cloud server. THANK YOU!