Closed cholzer79 closed 1 month ago
To all with this issue
This has been determined an unfortunate regression from v2.5.0-alpha-4
In v2.5.0-alpha-4
there was specific code to look for Docker use of --sync-dir
.. however somehow this got lost|dropped|erased between alpha-4 and alpha-5 ............
Please use the following instructions to clone this PR:
git clone https://github.com/abraunegg/onedrive.git
cd onedrive
git fetch origin pull/2901/head:pr2901
git checkout pr2901
Augment the above with the instructions here on building your own Docker container:
https://github.com/abraunegg/onedrive/blob/master/docs/docker.md#building-a-custom-docker-image
This has been tested with Docker via standard means, and via Docker Compose.
Please can you test this PR in your environment for resolution.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Describe the bug
https://github.com/abraunegg/onedrive/discussions/2887 When using a bind to give the docker container access to the data and conf folders on the host, the container will modify the conf file on every start causing a resync to be required. The solution is to enter the host path of the data folder inside the conf file for the sync_dir parameter.
Operating System Details
Client Installation Method
From Distribution Package
OneDrive Account Type
Personal
What is your OneDrive Application Version
v2.5.2-2-g3ad139a
What is your OneDrive Application Configuration
What is your 'curl' version
Where is your 'sync_dir' located
Local
What are all your system 'mount points'
What are all your local file system partition types
How do you use 'onedrive'
onedrive runs as docker container on my TrueNAS system. onedrive has been setup with Portainer.
Steps to reproduce the behaviour
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
No response
Additional context
No response