Hello,
with OMV v4 I was running a lot of docker containers without any problems. Now, after the upgrade (to OMV v5) I decided to switch from normal docker to docker compose.
Therefore I've installed docker and portainer via omv-extras. Furthermore I've updated to the latest docker-compose via CLI (according to GitHub).
My first docker-compose installation was Plex Media Server. Therefore I've created this docker-compose.yml:
---
version: "2"
services:
plex:
image: linuxserver/plex
container_name: plex
network_mode: host
environment:
- PUID=1001
- PGID=100
- VERSION=latest
volumes:
- /srv/dev-disk-by-label-work/appdata/dockers/plex:/config \
- /srv/dev-disk-by-label-work/appdata/dockers/plex/transcode:/transcode \
- /sharedfolders/multimedia1:/data1 \
- /sharedfolders/multimedia2:/data2 \
devices:
- /dev/dri:/dev/dri \
restart: unless-stopped
Alles anzeigen
Under the OMV-GUI I've changed the docker storage path from /var/lib/docker to /srv/dev-disk-by-label-work/appdata.
After starting of the docker, docker didn't use the stored path of the config folder (which I created before). All of the config files were stored under the docker storage path (before under /var/lib/docker) and not in the folder mentioned in the docker-compose.yml. Under portainer I can see two config-folders:
The config folder with the long number is located under
/sharedfolders/appdata/volumes/6d1aeb336ed1d0a1acbf07f3ba913b01d5a71395818bb0ecd98c2f2b72f077d4/_data
If I stop the container and try to remove the second config-folder (with the long name) I will get an error (via portainer).
Now my question. How can I solve this issue. Why does docker-compose create a new config-folder instead of using the one mentioned in the .yml file?
If I do the same with "normal docker" there's no problem. Everything is stored in the folder of the config-file.
Thanks in advance