mirror of
https://github.com/nextcloud/all-in-one.git
synced 2026-05-21 10:50:10 +00:00
Merge pull request #7606 from nextcloud/enh/7567/install-docs-unraid
readme: add install docs for unraid
This commit is contained in:
25
readme.md
25
readme.md
@@ -90,9 +90,10 @@ Included are:
|
||||
## How to use this?
|
||||
|
||||
The steps below are written for Linux. For platform-specific guidance see:
|
||||
- macOS: [How to run AIO on macOS](#how-to-run-aio-on-macos)
|
||||
- Windows: [How to run AIO on Windows](#how-to-run-aio-on-windows)
|
||||
- Synology DSM: [How to run AIO on Synology DSM](#how-to-run-aio-on-synology-dsm)
|
||||
- macOS: [How to run AIO on macOS?](#how-to-run-aio-on-macos)
|
||||
- Windows: [How to run AIO on Windows?](#how-to-run-aio-on-windows)
|
||||
- Unraid: [How to run AIO on Unraid?](#how-to-run-aio-on-unraid)
|
||||
- Synology DSM: [How to run AIO on Synology DSM?](#how-to-run-aio-on-synology-dsm)
|
||||
- TrueNAS SCALE: [Can I run AIO on TrueNAS SCALE?](#can-i-run-aio-on-truenas-scale)
|
||||
|
||||
> [!IMPORTANT]
|
||||
@@ -240,6 +241,7 @@ https://your-domain-that-points-to-this-server.tld:8443
|
||||
- [Guides](#guides)
|
||||
- [How to run AIO on macOS?](#how-to-run-aio-on-macos)
|
||||
- [How to run AIO on Windows?](#how-to-run-aio-on-windows)
|
||||
- [How to run AIO on Unraid?](#how-to-run-aio-on-unraid)
|
||||
- [How to run AIO on Synology DSM](#how-to-run-aio-on-synology-dsm)
|
||||
- [How to run AIO with Portainer?](#how-to-run-aio-with-portainer)
|
||||
- [Can I run AIO on TrueNAS SCALE?](#can-i-run-aio-on-truenas-scale)
|
||||
@@ -607,6 +609,23 @@ Also, you may be interested in adjusting Nextcloud's Datadir to store the files
|
||||
> [!NOTE]
|
||||
> Almost all commands in this project's documentation use `sudo docker ...`. Since `sudo` is not available on Windows, you simply remove `sudo` from the commands and they should work.
|
||||
|
||||
### How to run AIO on Unraid?
|
||||
|
||||
Generally on Unraid, before installing Nextcloud AIO, you should make sure to specify a directory for all docker related files instead of using the default docker image before continuing the installation process. See this guide for more details: https://forums.unraid.net/topic/103924-how-to-turn-my-docker-file-to-a-docker-folder/#comment-962317
|
||||
|
||||
Additionally, you might need to create a custom user script to start all sibling containers of AIO automatically whenever the server reboots (since the docker plugin in Unraid does not respect the normal docker restart-policy that is configured for all AIO containers). See the User scripts docs: https://docs.unraid.net/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers/#user-scripts-plugin. You would need to use a script like the one below and use the schedule option `@reboot` to start the containers automatically.
|
||||
```bash
|
||||
#!/bin/bash
|
||||
|
||||
# Wait 120 seconds for other server components to start correctly
|
||||
sleep 120
|
||||
|
||||
# Execute the actual command
|
||||
docker exec --env START_CONTAINERS=1 nextcloud-aio-mastercontainer /daily-backup.sh`
|
||||
```
|
||||
|
||||
Apart from that, the installation of AIO should work like on "normal" Linux. So refer to the Linux instructions for installation.
|
||||
|
||||
### How to run AIO on Synology DSM
|
||||
On Synology, there are two things different in comparison to Linux: instead of using `--volume /var/run/docker.sock:/var/run/docker.sock:ro`, you need to use `--volume /volume1/docker/docker.sock:/var/run/docker.sock:ro` to run it. You also need to add `--env WATCHTOWER_DOCKER_SOCKET_PATH="/volume1/docker/docker.sock"`to the docker run command of the mastercontainer (but before the last line `ghcr.io/nextcloud-releases/all-in-one:latest`). Additionally, you likely need to adjust the internally used api version. See [this documentation](#how-to-adjust-the-internally-used-docker-api-version). Apart from that it should work and behave the same like on Linux. Obviously the Synology Docker GUI will not work with that so you will need to either use SSH or create a user-defined script task in the task scheduler as the user 'root' in order to run the command.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user