Docker: Official nextcloud docker-compose

Created on 3 Mar 2017  路  3Comments  路  Source: nextcloud/docker

It would make sense to ship an official docker-compose from Nextcloud with the following features:

  • TLS
  • Cron
  • collabora

What do you think @SnowMB ?

Most helpful comment

I looked through the discussion and your comments and I like the ideas in https://github.com/docker-library/owncloud/pull/79.

It would be great to keep our base images (apache + fpm) simple and don't overcomplicate things by adding a million different tags. (e.g. If you would like to add a 'heavy' tag, you would have to do apache, fpm, apache-heavy, fpm-heavy multiplied by the number of versions we're offering.)
Instead we could document the possibility to build on the base images and add what the user needs via derived dockerfiles.

For example something like:

FROM nextcloud:apache
RUN apt-get update && apt-get install -y smbclient && rm -rf /var/lib/apt/lists/*

Or for cron:

FROM nextcloud:fpm

RUN apt-get update && apt-get install -y \
  supervisor \
  cron \
  && rm -rf /var/lib/apt/lists/*

RUN mkdir /var/log/supervisord /var/run/supervisord && \ 
  echo "*/15 * * * * su - www-data -s /bin/bash -c \"php -f /var/www/html/cron.php\""| crontab -

COPY supervisord.conf /etc/supervisor/supervisord.conf

CMD ["/usr/bin/supervisord"]

This would be a great way to let the user choose what he needs. (Personally I use exactly this method now, I was just to lazy to update my github repo 馃榿 )

For the official compose part:
After working with diffrent installations (at work and at home), I think it's not feasible. There are so many possibilities to configure even the simplest nextcloud installtion and it's depending heavily on the server architechture used (proxies, databases, ect.). We surely should add more examples (and I strongly agree that our documentation of how to use the fpm image must get better), but marking a docker-compose solution as "official" might be misleading and a bad idea. We should focus on giving the right examples so anyone can build the setup that suits him.

PS: any comment on the /var/www/html volume part? https://github.com/nextcloud/docker/pull/23

All 3 comments

I looked through the discussion and your comments and I like the ideas in https://github.com/docker-library/owncloud/pull/79.

It would be great to keep our base images (apache + fpm) simple and don't overcomplicate things by adding a million different tags. (e.g. If you would like to add a 'heavy' tag, you would have to do apache, fpm, apache-heavy, fpm-heavy multiplied by the number of versions we're offering.)
Instead we could document the possibility to build on the base images and add what the user needs via derived dockerfiles.

For example something like:

FROM nextcloud:apache
RUN apt-get update && apt-get install -y smbclient && rm -rf /var/lib/apt/lists/*

Or for cron:

FROM nextcloud:fpm

RUN apt-get update && apt-get install -y \
  supervisor \
  cron \
  && rm -rf /var/lib/apt/lists/*

RUN mkdir /var/log/supervisord /var/run/supervisord && \ 
  echo "*/15 * * * * su - www-data -s /bin/bash -c \"php -f /var/www/html/cron.php\""| crontab -

COPY supervisord.conf /etc/supervisor/supervisord.conf

CMD ["/usr/bin/supervisord"]

This would be a great way to let the user choose what he needs. (Personally I use exactly this method now, I was just to lazy to update my github repo 馃榿 )

For the official compose part:
After working with diffrent installations (at work and at home), I think it's not feasible. There are so many possibilities to configure even the simplest nextcloud installtion and it's depending heavily on the server architechture used (proxies, databases, ect.). We surely should add more examples (and I strongly agree that our documentation of how to use the fpm image must get better), but marking a docker-compose solution as "official" might be misleading and a bad idea. We should focus on giving the right examples so anyone can build the setup that suits him.

PS: any comment on the /var/www/html volume part? https://github.com/nextcloud/docker/pull/23

It would be great to keep our base images (apache + fpm) simple

@SnowMB Spot on. Happy to see Nextcloud docker images are in good hands.

@SnowMB you are right, closing in favor of #47

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nthack picture nthack  路  3Comments

tanja84dk picture tanja84dk  路  3Comments

all-the-good-ones-are-gone picture all-the-good-ones-are-gone  路  3Comments

christianvw picture christianvw  路  3Comments

mahnunchik picture mahnunchik  路  3Comments