-
-
Notifications
You must be signed in to change notification settings - Fork 849
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
Bug: Incredible slow #2754
Comments
@nathanredblur In your configuration you have also limited the client to 100 MB/s .... so I do not know if this is was intended or done due to testing .. but you should remove that configuration option. Options to solve:
Both these version have been 100% re-written to support multi-threading and provide significant performance improvements. If you are still stuck at only using 2 MB/s post using RC2 or pre-RC3 .. you need to raise a bug with your OS .. as the bug lies in their implementation of Docker and/or their network stack. |
I'm getting troubles to make it works. then, I upload the image to docker hub in order to use it with docker compose in my ZimaCube. but I'm getting this error: I suppose that It's related to this but I'm not sure how can I solve it in this scenario. |
Sounds like you need to raise another bug with your ZimaCube OS to allow you to build Docker images. |
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
Issue: OneDrive docker container is incredibly slow, and I stuck and frustrated, I don't know what else to do. the maximu speed is 2MB/s
This is my docker compose
My hardware is new and other dockers works faster downoading things.
![CleanShot 2024-07-14 at 06 40 27](https://private-user-images.githubusercontent.com/1273018/348539837-2ea81664-423d-42ea-b3be-57a206ea4297.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE4MzE0MDUsIm5iZiI6MTcyMTgzMTEwNSwicGF0aCI6Ii8xMjczMDE4LzM0ODUzOTgzNy0yZWE4MTY2NC00MjNkLTQyZWEtYjNiZS01N2EyMDZlYTQyOTcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcyNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MjRUMTQyNTA1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDc3YjkzZWI2Y2JmNDU1YWUzYTRiOGJmZmY1MzI0ZDc4ZjQ3YTkwYzAxNjI2MDQyYzk2MDA1ZDkxZTA4Mjc4OSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.2tXvVOILXPxF235t_J5hfSWxamyJpFiSAh74XCvzHIQ)
Operating System Details
Client Installation Method
From Source
OneDrive Account Type
Personal
What is your OneDrive Application Version
onedrive v2.4.25
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'
I'm running a docker
driveone/onedrive:latest
only this docker is reading and writing in this mounting point.My OneDrive account is active and running in other 3 devices (phone, and two PCs), none of them are storing data.
Steps to reproduce the behaviour
just run the docker in that zima cube linux.
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: