mirror of
https://github.com/nextcloud/docker.git
synced 2024-11-17 18:46:43 +01:00
Clarify Readme on bind volumes
Signed-off-by: Kaloyan Nikolov <tzerber@gmail.com>
This commit is contained in:
parent
178f8b65d3
commit
53c3162c83
1 changed files with 24 additions and 1 deletions
25
README.md
25
README.md
|
@ -87,13 +87,36 @@ If you want to use named volumes for all of these, it would look like this:
|
||||||
```console
|
```console
|
||||||
$ docker run -d \
|
$ docker run -d \
|
||||||
-v nextcloud:/var/www/html \
|
-v nextcloud:/var/www/html \
|
||||||
-v apps:/var/www/html/custom_apps \
|
-v custom_apps:/var/www/html/custom_apps \
|
||||||
-v config:/var/www/html/config \
|
-v config:/var/www/html/config \
|
||||||
-v data:/var/www/html/data \
|
-v data:/var/www/html/data \
|
||||||
-v theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \
|
-v theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \
|
||||||
nextcloud
|
nextcloud
|
||||||
```
|
```
|
||||||
|
|
||||||
|
If you'd prefer to use bind mounts instead of named volumes, for instance, when working with different device or network mounts for user data files and configuration:
|
||||||
|
```console
|
||||||
|
$ docker run -d \
|
||||||
|
-v $(pwd)/nextcloud:/var/www/html \
|
||||||
|
-v $(pwd)/custom_apps:/var/www/html/custom_apps \
|
||||||
|
-v $(pwd)/config:/var/www/html/config \
|
||||||
|
-v $(pwd)/data:/var/www/html/data \
|
||||||
|
-v $(pwd)/theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \
|
||||||
|
nextcloud
|
||||||
|
```
|
||||||
|
|
||||||
|
Here’s the same example using Docker's more detailed `--mount`. Note that with `-v` or `--volume`, the specified folders are created automatically if they don't exist. However, when using `--mount` for bind mounts, the directories must already exist on the host, or Docker will return an error.
|
||||||
|
```console
|
||||||
|
$ docker run -d \
|
||||||
|
--mount type=bind,source=$(pwd)/nextcloud,target=/var/www/html \
|
||||||
|
--mount type=bind,source=$(pwd)/custom_apps,target=/var/www/html/custom_apps \
|
||||||
|
--mount type=bind,source=$(pwd)/config,target=/var/www/html/config \
|
||||||
|
--mount type=bind,source=$(pwd)/data,target=/var/www/html/data \
|
||||||
|
--mount type=bind,source=$(pwd)/theme,target=/var/www/html/themes/<YOUR_CUSTOM_THEME> \
|
||||||
|
nextcloud
|
||||||
|
```
|
||||||
|
The examples above use the current directory for bind mounts. If this isn't suitable, you can modify the paths by using either a relative or absolute path. Additionally, do not mix the `apps` and `custom_apps` folders. These folders contain different sets of apps, and mixing them will result in a broken installation. While upgrades\recovery may sometimes still be possible, this configuration is likely to cause issues.
|
||||||
|
|
||||||
### Custom volumes
|
### Custom volumes
|
||||||
|
|
||||||
If mounting additional volumes under `/var/www/html`, you should consider:
|
If mounting additional volumes under `/var/www/html`, you should consider:
|
||||||
|
|
Loading…
Reference in a new issue