An application configuration change has been detected - and I dont know why

[cholzer79]

Today I deployed the docker version of onedrive (driveone/onedrive:edge also tried driveone/onedrive:lastet) using Portainer.
The only thing I use the config file for is to configure the webhook (can I use the ENV to configure that instead of the conf?).
The initial resync worked great! All files were downloaded, webhoook works, changes got pushed correctly and quickly.

Then I stopped the onedrive container, set the ONEDRIVE_RESYNC ENV to 0 and launched the container again.

Now i get this:

usermod: no changes
# Running container as user: onedrive
# Base Args: --monitor
# Changing ownership permissions on /onedrive/data and /onedrive/conf to onedrive:onedrive
# Launching 'onedrive' as onedrive via gosu
Reading configuration file: /onedrive/conf/config
Configuration file successfully loaded
An application configuration change has been detected where a --resync is required

Is it possible that this is caused by the Changing ownership permissions step?
I have noticed that the modification date of the conf file was changed when the container started (or is restarted).

I am using binds.

/edit
in case someone else comes across this, adding the host path from the data bind to the conf file as sync_dir fixes the problem. :)
#2839 (reply in thread)

[abraunegg]

@cholzer79
Please raise a bug report

[cholzer79]

Done. Not sure if I did it correctly as some parts of the template dont quite seem to apply to the docker version of onedrive.
#2889