Closed robdejonge closed 2 months ago
Please update your environment variables list in docker-compose.yaml
to set ENV_CONFIG_FILE_PATH=/config/config.yaml
and PGID=1000
(not GUID).
Sorry for the bug label, when I clicked 'New issue' I did not see the ability for a support request.
I feel a bit silly, as it's clearly in the documentation right there. But this must have been a recent change to the requirements, as previously it was all just working? Anyway, it's all working again just fine now.
Thanks for your help!
No worries. Yes, it is a recent change mentioned in v1.20.0 breaking changes
Describe the bug I've been using this tool for several years without any problem, and recently it has stopped working. For the life of me, I can't figure out what I am doing wrong.
To Reproduce I normally start the container once daily to do a sync, and it then waits in the 'stopped' state until it gets started again. This has always worked really well, but for some reason I can't get it working again.
$config/session_data
foldersync_interval
to 300 so that I have time to get the password storeddocker compose up
)retry_login_interval
to (tried -1 and 333)./app/config.yaml
which DOES mention that 600 and notification config. So it seems the container is preferring this file for some reason and not the$config/config.yaml
??/config/session_data
files./app/config.yaml
file.Expected behavior I expect it to follow directions provided in /
config/config.yaml
rather than/app/config.yaml
.Configuration My docker-compose.yaml:
My config.yaml:
There is no message on the container output clarifying which config file is being used, but I'm fairly certain the
/app/config.yaml
is being used. Why this happens, I do not know. Maybe my config file is being dismissed because of an error?Additional context I've tried changing permissions to 777 for
/opt/icloud-drive-files
and files within, to avoid permissions being an issue.(I'm aware this is more likely a configuration error on my part, but I've had several runs at this and have no idea what I'm doing wrong ... and about to give up on using this!)