kopia lustrzana https://github.com/linuxserver/docker-documentation
250 wiersze
15 KiB
Markdown
250 wiersze
15 KiB
Markdown
---
|
|
title: nextcloud
|
|
---
|
|
<!-- DO NOT EDIT THIS FILE MANUALLY -->
|
|
<!-- Please read the https://github.com/linuxserver/docker-nextcloud/blob/master/.github/CONTRIBUTING.md -->
|
|
|
|
# [linuxserver/nextcloud](https://github.com/linuxserver/docker-nextcloud)
|
|
|
|
[](https://scarf.sh/gateway/linuxserver-ci/docker/linuxserver%2Fnextcloud)
|
|
[](https://github.com/linuxserver/docker-nextcloud)
|
|
[](https://github.com/linuxserver/docker-nextcloud/releases)
|
|
[](https://github.com/linuxserver/docker-nextcloud/packages)
|
|
[](https://gitlab.com/linuxserver.io/docker-nextcloud/container_registry)
|
|
[](https://quay.io/repository/linuxserver.io/nextcloud)
|
|
[](https://hub.docker.com/r/linuxserver/nextcloud)
|
|
[](https://hub.docker.com/r/linuxserver/nextcloud)
|
|
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-nextcloud/job/master/)
|
|
[](https://ci-tests.linuxserver.io/linuxserver/nextcloud/latest/index.html)
|
|
|
|
[Nextcloud](https://nextcloud.com/) 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.
|
|
|
|
## Supported Architectures
|
|
|
|
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
|
|
|
|
Simply pulling `lscr.io/linuxserver/nextcloud:latest` 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:
|
|
|
|
| Architecture | Available | Tag |
|
|
| :----: | :----: | ---- |
|
|
| x86-64 | ✅ | amd64-\<version tag\> |
|
|
| arm64 | ✅ | arm64v8-\<version tag\> |
|
|
| armhf | ❌ | |
|
|
|
|
## Version Tags
|
|
|
|
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
|
|
|
|
| Tag | Available | Description |
|
|
| :----: | :----: |--- |
|
|
| latest | ✅ | Stable Nextcloud releases |
|
|
| develop | ✅ | Beta Nextcloud pre-releases *only* |
|
|
## Application Setup
|
|
|
|
Access the webui at `https://<your-ip>:443`, for more information check out [Nextcloud](https://nextcloud.com/).
|
|
|
|
### Updating Nextcloud
|
|
|
|
Updating Nextcloud is done by pulling the new image, and recreating the container with it.
|
|
|
|
It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16.
|
|
|
|
Since all data is stored in the `/config` and `/data` volumes, nothing gets lost. The startup script will check for the version in your volume and the installed docker version. If it finds a mismatch, it automatically starts the upgrade process.
|
|
|
|
### Collaborative Editing
|
|
|
|
Nextcloud's built-in collaborative editing packages (Collabora/CODE and OnlyOffice) only work on x86_64 systems with glibc, and therefore they are not compatible with our images. You should create separate containers for them and set them up in Nextcloud with their respective connector addons.
|
|
|
|
If (auto) installed, those built-in packages may cause instability and should be removed.
|
|
|
|
### Custom App Directories
|
|
|
|
If you are [using custom app directories](https://docs.nextcloud.com/server/latest/admin_manual/apps_management.html#using-custom-app-directories) you will need to make the custom folder(s) you are using available to the web server. The recommended way to do this with our container is to add a volume. Ex:
|
|
|
|
```yaml
|
|
volumes:
|
|
- /path/to/your_custom_apps_folder:/app/www/public/your_custom_apps_folder
|
|
```
|
|
|
|
Afterwards, you can set `"path" => OC::$SERVERROOT . "/your_custom_apps_folder",` in your `config.php` file, per the [official documentation](https://docs.nextcloud.com/server/latest/admin_manual/apps_management.html#using-custom-app-directories).
|
|
|
|
### Strict reverse proxies
|
|
|
|
This image uses a self-signed certificate by default. This naturally means the scheme is `https`.
|
|
If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
|
|
|
|
## Usage
|
|
|
|
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
|
|
|
|
### docker-compose (recommended, [click here for more info](https://docs.linuxserver.io/general/docker-compose))
|
|
|
|
```yaml
|
|
---
|
|
version: "2.1"
|
|
services:
|
|
nextcloud:
|
|
image: lscr.io/linuxserver/nextcloud:latest
|
|
container_name: nextcloud
|
|
environment:
|
|
- PUID=1000
|
|
- PGID=1000
|
|
- TZ=Etc/UTC
|
|
volumes:
|
|
- /path/to/appdata:/config
|
|
- /path/to/data:/data
|
|
ports:
|
|
- 443:443
|
|
restart: unless-stopped
|
|
```
|
|
|
|
### docker cli ([click here for more info](https://docs.docker.com/engine/reference/commandline/cli/))
|
|
|
|
```bash
|
|
docker run -d \
|
|
--name=nextcloud \
|
|
-e PUID=1000 \
|
|
-e PGID=1000 \
|
|
-e TZ=Etc/UTC \
|
|
-p 443:443 \
|
|
-v /path/to/appdata:/config \
|
|
-v /path/to/data:/data \
|
|
--restart unless-stopped \
|
|
lscr.io/linuxserver/nextcloud:latest
|
|
|
|
```
|
|
|
|
## Parameters
|
|
|
|
Docker 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.
|
|
|
|
### Ports (`-p`)
|
|
|
|
| Parameter | Function |
|
|
| :----: | --- |
|
|
| `443` | WebUI |
|
|
|
|
### Environment Variables (`-e`)
|
|
|
|
| Env | Function |
|
|
| :----: | --- |
|
|
| `PUID=1000` | for UserID - see below for explanation |
|
|
| `PGID=1000` | for GroupID - see below for explanation |
|
|
| `TZ=Etc/UTC` | specify a timezone to use, see this [list](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List). |
|
|
|
|
### Volume Mappings (`-v`)
|
|
|
|
| Volume | Function |
|
|
| :----: | --- |
|
|
| `/config` | Nextcloud configs. |
|
|
| `/data` | Your personal data. |
|
|
|
|
#### Miscellaneous Options
|
|
|
|
| Parameter | Function |
|
|
| :-----: | --- |
|
|
|
|
## Environment variables from files (Docker secrets)
|
|
|
|
You can set any environment variable from a file by using a special prepend `FILE__`.
|
|
|
|
As an example:
|
|
|
|
```bash
|
|
-e FILE__PASSWORD=/run/secrets/mysecretpassword
|
|
```
|
|
|
|
Will set the environment variable `PASSWORD` based on the contents of the `/run/secrets/mysecretpassword` file.
|
|
|
|
## Umask for running applications
|
|
|
|
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
|
|
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
|
|
|
## User / Group Identifiers
|
|
|
|
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:
|
|
|
|
```bash
|
|
$ id username
|
|
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
|
```
|
|
|
|
## Docker Mods
|
|
|
|
[](https://mods.linuxserver.io/?mod=nextcloud "view available mods for this container.") [](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
|
|
|
|
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
|
|
|
|
## Support Info
|
|
|
|
* 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" }}' lscr.io/linuxserver/nextcloud:latest`
|
|
|
|
## Versions
|
|
|
|
* **31.08.23:** - Re-add updatenotification app. This allows users to be notified for app updates, but also notifies for NextCloud updates. Updating NextCloud via the web UI is not supported when using this image.
|
|
* **14.08.23:** - Add develop branch.
|
|
* **25.06.23:** - Move Nextcloud installation inside container. Remove CLI updater. [See changes announcement](https://info.linuxserver.io/issues/2023-06-25-nextcloud/).
|
|
* **21.06.23:** - Existing users should update `/config/nginx/site-confs/default.conf` - Security fix for real ip settings.
|
|
* **25.05.23:** - Rebase to Alpine 3.18, deprecate armhf.
|
|
* **13.04.23:** - Move ssl.conf include to default.conf.
|
|
* **21.03.23:** - Add php81-sysvsem as new dep for v26. Update default X-Robots-Tag to `noindex, nofollow``.
|
|
* **02.03.23:** - Set permissions on crontabs during init.
|
|
* **20.01.23:** - Rebase to alpine 3.17 with php8.1.
|
|
* **10.10.22:** - Rebasing to alpine 3.15 with php8. Restructure nginx configs ([see changes announcement](https://info.linuxserver.io/issues/2022-08-20-nginx-base)).
|
|
* **30.09.22:** - Disabled `output_buffering` as per [nextcloud docs](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html
|
|
* **21.05.22:** - Update version check endpoint.
|
|
* **28.04.22:** - Increase OPCache interned strings buffered setting to 16.
|
|
* **14.04.22:** - Nginx default site config updated for v23 (existing users should delete `/config/nginx/site-confs/default.conf` and restart the container). Fix LDAP connection.
|
|
* **11.09.21:** - Rebasing to alpine 3.14
|
|
* **21.03.21:** - Publish `php8` tag for testing.
|
|
* **25.02.21:** - Nginx default site config updated for v21 (existing users should delete `/config/nginx/site-confs/default.conf` and restart the container).
|
|
* **21.01.21:** - Fix php iconv (was breaking the mail addon). If installed, attempt to remove broken CODE Server app during startup.
|
|
* **20.01.21:** - Increase php fcgi timeout to prevent 504 Gateway timeout errors (existing users should delete `/config/nginx/site-confs/default.conf` and restart the container).
|
|
* **16.01.21:** - Rebasing to alpine 3.13. Users with issues on 32-bit arm, [see this article](https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal-and-alpine-3-13).
|
|
* **12.08.20:** - Various updates to default site config, including added support for webfinger (existing users should delete `/config/nginx/site-confs/default.conf` and restart the container).
|
|
* **03.06.20:** - Rebasing to alpine 3.12
|
|
* **03.06.20:** - Add php7-bcmath and php7-fileinfo
|
|
* **31.05.20:** - Add aliases for occ and updater.phar
|
|
* **31.03.20:** - Allow crontab to be user customized, fix logrotate.
|
|
* **17.01.20:** - Updated php.ini defaults and site config, including an optional HSTS directive (existing users should delete `/config/nginx/site-confs/default.conf` and restart the container).
|
|
* **19.12.19:** - Rebasing to alpine 3.11.
|
|
* **18.11.19:** - Nginx default site config updated for v17 (existing users should delete `/config/nginx/site-confs/default.conf` and restart the container).
|
|
* **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.conf` 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.
|