-
-
Notifications
You must be signed in to change notification settings - Fork 868
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Logout possible when using a Docker container #1185
Comments
@Orbocom Additionally - you have this:
Do not do this. What this means is every time your Docker container starts you are deleting your local sync state and performing a clean sync. There is no need to do this unless the application tells you to run --resync you you really want to perform this action. |
Please can you test the following PR:
When running the PR, your version should be: As you are running Docker, you will need to manually rebuild your Docker container using this PR. Use Usage Example:
If you can test and provide feedback that would be greatly appreciated. |
Thank you for your quick response; highly appreciated! |
Any update in testing this PR? |
Hi,
My apologies, I am a total Newby in this field. Struggling myself through
this new world of compiling and building containers....
Took and takes some in depth reading.
Nevertheless, making progress. Hope to get back to you soon.
Op za 19 dec. 2020 21:28 schreef abraunegg <notifications@github.com>:
… @Orbocom <https://github.com/Orbocom>
Any update in testing this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1185 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARFBPVF7RNIEP4A3AR5BEZ3SVUEIVANCNFSM4U57LMAA>
.
|
Hope this provides you with some usable output Compiling seemed to work in the correct way. The "docker build" process caused errors (see bottom of log); no idea how to resolve this. Docker build Log Output
|
Unsure. It looks like the build process is not pulling in the correct requirements. What I will do is push this to 'master', you should then just be able to rebuild your client without issue by pulling down the latest image and re-testing that way. |
This is now merged, to you will be able to test the 'latest' Docker image once they have rebuilt - usually within the next 30 mins. |
Pulled the updated image and ran the container. |
|
|
Sorry for the mess. |
This tells me you need to use also
If not, you need to start it with:
Please read the Docker usage document for more details. |
Closing issue as PR merged into 'master', and original issue fixed |
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. |
onedrive app has ran succesfully in docker container.
After change of MS OneDrive password, docker container onedrive stops immediately after start, requesting for --logout
As container has stopped I cannot request logout, therefore cannot reauthorize.
System
make install
by missing directory #64-UbuntuApplication Log Output:
The text was updated successfully, but these errors were encountered: