-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Thank you for this fantastic container! I noticed some unexpected behavior, detailed below. I wanted to bring it to your attention, as I didn't know if this behavior was intended. I believe I have found a suitable workaround, but I am open to suggestions if there is a better way to do it. Thanks!
Unexpected behavior:
Everything worked as expected when using the recommended bind mount, /docker/plex/config:/config. For maximum portability, I wanted to use a named volume to sync this directory with my Google Drive using the rclone plugin, as follows:
services:
plex:
...
volumes:
- config:/config
...
volumes:
config:
driver: rclone
driver_opts:
remote: my-google-drive:path/to/config
allow_other: "true"
vfs_cache_mode: full
poll_interval: 0
However, with this configuration, the Library directory is not created or populated (even after deleting and re-creating the container, as I understand it may only be created on the first run).
Workaround:
I was able to manually create another named volume for the Library and map it to /config/Library, which caused it to populate as expected, using the following addition:
services:
plex:
...
volumes:
- config:/config
- type: volume
source: config
target: /config/Library
volume:
subpath: Library