Do I need to authorize OneDrive account when I just need to sync SharePoint in a Docker container? #1996
-
|
As per Docker, OneDrive authorization needs to be done the moment the client container gets started. However, we need another command In my case, I set up the container just to sync with SharePoint, I interrupted the OneDrive authorization process using Ctrl+C, and did However,
Is this because that I skipped the OneDrive authorization? How can I adapt the configuration to my SharePoint-only use case with Docker? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Correct .. it is because you did not follow the correct process. What you need to do is run the client on a totally separate machine to get all the SharePoint details needed to configure your Docker Containers .. dont try and get all the details from inside a Docker Container ... will just lead to frustration and failure. Follow the documentation on starting and running the containers as well. This is the documented process that works |
Beta Was this translation helpful? Give feedback.
-
|
But following the documentation leads me to register with my ODFB account. Do you mean that I should copy the configuration file from another machine that syncs with the SharePoint site already to the container to be synced with SP and then run `onedrive --resync` because of the change of `drive_id` before a final `onedrive --monitor` ?
…________________________________
From: abraunegg ***@***.***>
Sent: Wednesday, June 8, 2022 4:25:08 PM
To: abraunegg/onedrive ***@***.***>
Cc: Johnny Song ***@***.***>; Mention ***@***.***>
Subject: Re: [abraunegg/onedrive] Do I need to authorize OneDrive account when I just need to sync SharePoint in a Docker container? (Discussion #1996)
@everwisher<https://github.com/everwisher>
Is this because that I skipped the OneDrive authorization? How can I adapt the configuration to my SharePoint-only use case with Docker?
Correct .. it is because you did not follow the correct process.
What you need to do is run the client on a totally separate machine to get all the SharePoint details needed to configure your Docker Containers .. dont try and get all the details from inside a Docker Container ... will just lead to frustration and failure.
Follow the documentation on starting and running the containers as well. This is the documented process that works
—
Reply to this email directly, view it on GitHub<#1996 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADAUWI3IRWYJAVEO2ETRNQLVOD6SJANCNFSM5YHALYHA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Correct ... each Docker container needs to be authenticated and authorised from a security scope
If you copy 'refresh_token' and only this file to your Docker 'config' folder this will negate the need to 'authenticate' that new Docker Container
Do not do this ..... do not use You are also still starting the Docker container and application in the incorrect manner using Docker .. please read the documentation and follow what the documentation says on how to run the Docker container |
Beta Was this translation helpful? Give feedback.
@everwisher
Correct .. it is because you did not follow the correct process.
What you need to do is run the client on a totally separate machine to get all the SharePoint details needed to configure your Docker Containers .. dont try and get all the details from inside a Docker Container ... will just lead to frustration and failure.
Follow the documentation on starting and running the containers as well. This is the documented process that works