The LinuxServer.io team brings you another container release featuring :-

• regular and timely application updates
• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• regular security updates

Find us at:

• Blog - all the things you can do with our containers including How-To guides, opinions and much more!
• Discord - realtime support / chat with the community and the team.
• Discourse - post on our community forum.
• Fleet - an online web interface which displays all of our maintained images.
• Podcast - on hiatus. Coming back soon (late 2018).
• Open Collective - please consider helping us by either donating or contributing to our budget

Nextcloud gives you access to all your files wherever you are.

Where are your photos and documents? With Nextcloud you pick a server of your choice, at home, in a data center or at a provider. And that is where your files will be. Nextcloud runs on that server, protecting your data and giving you access from your desktop or mobile devices. Through Nextcloud you also access, sync and share your existing data on that FTP drive at the office, a Dropbox or a NAS you have at home.

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling linuxserver/nextcloud should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Here are some example snippets to help you get started creating a container.

docker create \
  --name=nextcloud \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 443:443 \
  -v </path/to/appdata>:/config \
  -v <path/to/data>:/data \
  --restart unless-stopped \
  linuxserver/nextcloud

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - </path/to/appdata>:/config
      - <path/to/data>:/data
    ports:
      - 443:443
    restart: unless-stopped

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

When using 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 any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

Access the webui at https://<your-ip>:443, for more information check out Nextcloud.

In order to update nextcloud version, first make sure you are using the latest docker image, and then perform the in app gui update. Docker image update and recreation of container alone won't update nextcloud version.

If you are not customizing our default nginx configuration you will need to remove the file:

/config/nginx/site-confs/default

Then restart the container to replace it with the latest one.

• Shell access whilst the container is running: docker exec -it nextcloud /bin/bash
• To monitor the logs of the container in realtime: docker logs -f nextcloud
• container version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' nextcloud
• image version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/nextcloud

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

• Update the image: docker pull linuxserver/nextcloud
• Stop the running container: docker stop nextcloud
• Delete the container: docker rm nextcloud
• Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
• Start the new container: docker start nextcloud
• You can also remove the old dangling images: docker image prune

• Update all images: docker-compose pull
  • or update a single image: docker-compose pull nextcloud
• Let compose update all containers as necessary: docker-compose up -d
  • or update a single container: docker-compose up -d nextcloud
• You can also remove the old dangling images: docker image prune

• Pull the latest image at its tag and replace it with the same env variables in one run:

  docker run --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  --run-once nextcloud
  

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

• You can also remove the old dangling images: docker image prune

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-nextcloud.git
cd docker-nextcloud
docker build \
  --no-cache \
  --pull \
  -t linuxserver/nextcloud:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

• 28.10.19: - Change cronjob to run every 5 minutes.
• 24.10.19: - Nginx default site config updated due to CVE-2019-11043 (existing users should delete /config/nginx/site-confs/default and restart the container).
• 14.07.19: - Download nextcloud during build time.
• 28.06.19: - Rebasing to alpine 3.10.
• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
• 27.02.19: - Updating base nginx config to sync up with v15 requirements.
• 22.02.19: - Rebasing to alpine 3.9.
• 28.01.19: - Add pipeline logic and multi arch.
• 25.01.19: - Add php7-phar for occ upgrades.
• 05.09.18: - Rebase to alpine 3.8.
• 11.06.18: - Use latest rather than specific version for initial install.
• 26.04.18: - Bump default install to 13.0.1.
• 06.02.18: - Bump default install to 13.0.0.
• 26.01.18: - Rebase to alpine 3.7, bump default install to 12.0.5.
• 12.12.17: - Bump default install to 12.0.4, fix continuation lines.
• 15.10.17: - Sed php.ini for opcache requirements in newer nextcloud versions.
• 20.09.17: - Bump default install to 12.0.3.
• 19.08.17: - Bump default install to 12.0.2.
• 25.05.17: - Rebase to alpine 3.6.
• 22.05.17: - Update to nextcloud 12.0, adding required dependecies and note about commenting out SAMEORIGIN; line.
• 03.05.17: - Use community repo of memcache.
• 07.03.17: - Release into main repository and upgrade to php7 and Alpine 3.5.