2018-06-02 12:13:30 +02:00
|
|
|
If you want to use another folder for the vmail-volume, you can create an `docker-compose.override.yml` file and add:
|
|
|
|
```
|
2018-06-05 20:41:27 +02:00
|
|
|
version: '2.1'
|
2018-06-02 12:13:30 +02:00
|
|
|
volumes:
|
|
|
|
vmail-vol-1:
|
|
|
|
driver_opts:
|
|
|
|
type: none
|
|
|
|
device: /data/mailcow/vmail
|
|
|
|
o: bind
|
|
|
|
```
|
2018-10-26 23:49:37 +02:00
|
|
|
|
2018-12-06 22:40:18 +01:00
|
|
|
Moving an existing vmail folder:
|
2019-02-23 09:23:29 +01:00
|
|
|
|
2018-12-06 22:40:18 +01:00
|
|
|
- Locate the current vmail folder by its "Mountpoint" attribute: `docker volume inspect mailcowdockerized_vmail-vol-1`
|
|
|
|
- Copy the `_data` folder to the new folder using `cp -a`, `rsync -a` or a similar non strcuture breaking copy command
|
|
|
|
- Stop mailcow by executing `docker-compose down` from within your mailcow root folder (e.g. "/opt/mailcow-dockerized")
|
|
|
|
- Create the file `docker-compose.override.yml`
|
|
|
|
- Delete the current vmail folder: `docker volume rm mailcowdockerized_vmail-vol-1`
|
|
|
|
- Start mailcow by executing `docker-compose up -d` from within your mailcow root folder (e.g. "/opt/mailcow-dockerized")
|