Closed strass closed 11 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
bump
I'll be honest, this would be a very low priority for us as we already have a sizeable backlog.
The config folder is meant to hold container files in a persistent manner. It's not meant for storing non-container or user files. Definitely not meant for storing symlinks that point to files that are not mounted/accessible inside the container. Therefore this is an extreme edge case.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
I co-locate my docker-compose file alongside the /config file in the plex image (
/opt/config/plex:/config:rw
). For organizational purposes I've recently started symlinking my source of truth from a git repository into the config directory so that changes are propagated automatically.Since doing that I have begun seeing this error on container startup:
Expected Behavior
I would expect that the chown script can deal with symlinked files and won't prevent plex startup.
Steps To Reproduce
Bind the /config folder in the container to a directory in your host that contains your docker-compose file Symlink the docker-compose file in from another directory Start container
Environment
CPU architecture
x86-64
Docker creation
Container logs