onedrive – abraunegg
OneDrive Linux 客户端
关键指标一览
主题标签
README 详细介绍
OneDrive Client for Linux
<img src="https://img.shields.io/github/v/release/abraunegg/onedrive?logo=github" alt="Version" class="ra0-md-img" loading="lazy" />
<img src="https://img.shields.io/github/release-date/abraunegg/onedrive?logo=github" alt="Release Date" class="ra0-md-img" loading="lazy" />
<img src="https://github.com/abraunegg/onedrive/actions/workflows/testbuild.yaml/badge.svg" alt="Linux Test Build" class="ra0-md-img" loading="lazy" />
<img src="https://github.com/abraunegg/onedrive/actions/workflows/smoke-test.yaml/badge.svg" alt="Linux Smoke Test" class="ra0-md-img" loading="lazy" />
<img src="https://github.com/abraunegg/onedrive/actions/workflows/docker.yaml/badge.svg" alt="Build Docker Images" class="ra0-md-img" loading="lazy" />
<img src="https://img.shields.io/docker/pulls/driveone/onedrive?logo=docker" alt="Docker Pulls" class="ra0-md-img" loading="lazy" />
A fully featured, free, and actively maintained Microsoft OneDrive client that seamlessly supports OneDrive Personal, OneDrive for Business, Microsoft 365 (formerly Office 365), and SharePoint document libraries.
Designed for maximum flexibility and reliability, this powerful and highly configurable client works across all major Linux distributions, FreeBSD and OpenBSD. It can also be deployed in containerised environments using Docker or Podman. Supporting both one-way and two-way synchronisation modes, the client provides secure and efficient file syncing with Microsoft OneDrive services — tailored to suit both desktop and server environments.
Project Background
This project originated as a fork of the skilion client in early 2018, after a number of proposed improvements and bug fixes — including Pull Requests #82 and #314 — were not merged and development activity of the skilion client had largely stalled. While it’s unclear whether the original developer was unavailable or had stepped away from the project - bug reports and feature requests remained unanswered for extended periods. In 2020, the original developer (skilion) confirmed they had no intention of maintaining or supporting their work (reference).
The original skilion repository was formally archived and made read-only on GitHub in December 2024. While still publicly accessible as a historical reference, an archived repository is no longer maintained, cannot accept contributions, and reflects a frozen snapshot of the codebase. The last code change to the skilion client was merged in November 2021; however, active development had slowed significantly well before then. As such, the skilion client should no longer be considered current or supported — particularly given the major API changes and evolving Microsoft OneDrive platform requirements since that time.
Under the terms of the GNU General Public License (GPL), forking and continuing development of open source software is fully permitted — provided that derivative works retain the same license. This client complies with the original GPLv3 licensing, ensuring the same freedoms granted by the original project remain intact.
Since forking in early 2018, this client has evolved into a clean re-imagining of the original codebase, resolving long-standing bugs and adding extensive new functionality to better support both personal and enterprise use cases to interact with Microsoft OneDrive from Linux, FreeBSD and OpenBSD platforms.
Features
Broad Microsoft OneDrive Compatibility
- Works with OneDrive Personal, OneDrive for Business, and Microsoft SharePoint Libraries.
- Full support for shared folders and files across both Personal and Business accounts.
- Supports single-tenant and multi-tenant Microsoft Entra ID environments.
- Compatible with national cloud deployments:
- Microsoft Cloud for US Government
- Microsoft Cloud Germany
- Azure/Office 365 operated by VNET in China
Flexible Synchronisation Modes
- Bi-directional sync (default) - keeps local and remote data fully aligned.
- Upload-only mode - only uploads local changes; does not download remote changes.
- Download-only mode - only downloads remote changes; does not upload local changes.
- Dry-run mode - test configuration changes safely without modifying files.
- Safe conflict handling minimises data loss by creating local backups whenever this is determined to be the safest conflict-resolution strategy.
Client-Side Filtering & Granular Sync Control
- Comprehensive rules-based client-side filtering (inclusions, exclusions, wildcard
, globbing*). - Filter specific files, folders, or patterns to tailor precisely what is synced with Microsoft OneDrive.
- Efficient cached sync state for fast decision-making during large or complex sync sets.
Real-Time Monitoring & Online Change Detection
- Near real-time processing of cloud-side changes using native WebSocket support.
- Webhook support for environments where WebSockets are unsuitable (manual setup).
- Real-time local change monitoring via inotify.
Data Safety, Recovery & Integrity Protection
- Implements the FreeDesktop.org Trash specification, enabling recovery of items deleted locally due to online deletion.
- Strong safeguards to prevent accidental remote deletion or overwrite after configuration changes.
- Interruption-tolerant uploads and downloads, automatically resuming transfers.
- Integrity validation for every file transferred.
Modern Authentication Support
- Standard OAuth2 Native Client Authorisation Flow (default), supporting browser-based login, multi-factor authentication (MFA), and modern Microsoft account security requirements.
- OAuth2 Device Authorisation Flow for Microsoft Entra ID accounts, ideal for headless systems, servers, and terminal-only environments.
- Intune Single Sign-On (SSO) using the Microsoft Identity Device Broker (IDB) via D-Bus, enabling seamless enterprise authentication without manual credential entry.
Performance, Efficiency & Resource Management
- Multi-threaded file transfers for significantly improved sync speeds.
- Bandwidth rate limiting to control network consumption.
- Highly efficient processing with state caching, reducing API traffic and improving performance.
Desktop Integration & User Experience
- libnotify desktop notifications for sync events, warnings, and errors.
- Registers the OneDrive folder as a sidebar location in supported file managers, complete with a distinctive icon.
- Works seamlessly in GUI and headless/server environments. A GUI is only required for Intune SSO, notifications, and sidebar integration; all other features function without graphical support.
What's missing
- Ability to encrypt/decrypt files on-the-fly when uploading/downloading files from OneDrive
- Support for Windows 'On-Demand' functionality so file is only downloaded when accessed locally
External Enhancements
- A GUI for configuration management: OneDrive Client for Linux GUI
- Colorful log output terminal modification: OneDrive Client for Linux Colorful log Output
- System Tray Icon: OneDrive Client for Linux System Tray Icon
Frequently Asked Questions
Refer to Frequently Asked Questions
Have a question
If you have a question or need something clarified, please raise a new discussion post here
Supported Application Version
Support is only provided for the current application release version or newer 'master' branch versions.
The current release version is: <img src="https://img.shields.io/github/v/release/abraunegg/onedrive" alt="Version" class="ra0-md-img" loading="lazy" />
To check your version, run: onedrive --version. Ensure you are using the current release or compile the latest version from the master branch if needed.
If you are using an older version, you must upgrade to the current release or newer to receive support.
Documentation and Configuration Assistance
OneDrive Client for Linux includes a rich set of documentation covering installation, configuration options, advanced usage, and integrations. These resources are designed to help new users get started quickly and to give experienced users full control over advanced behaviour. If you are changing configuration, running in production, or using Business/SharePoint features, you should be reading these documents. All documentation is maintained in the <code class="ra0-md-code">docs/</code> directory of this repository.
Getting Started
Installation
Learn how to install the client on various systems — from distribution packages to building from source. Please read the Install Guide
Basic Usage & Configuration
Covers initial authentication, default settings, basic operational instructions, frequently asked 'how to' questions, and how to tailor the application configuration. Please read the Usage Guide
Advanced Configuration
Application Configuration Options
Full reference for every config option (with descriptions, defaults, and examples) to customise sync behaviour precisely. Please read the Application Configuration Options Guide
Advanced Usage
Tips for creating multiple config profiles, custom sync rules, daemon setups, selective sync, dual-booting with Microsoft Windows and more. Please read the Advanced Usage Guide
Special Use Cases
Business Shared Items
Configuring sync for OneDrive Business shared items (files and folders). Please read the Business Shared Items Guide
SharePoint & Office 365 Libraries
Instructions for syncing SharePoint document libraries (Business or Education tenants). Please read the SharePoint Library Guide
National Cloud support
Instructions for environments like Microsoft Cloud Germany or US Government cloud endpoints. Please read the National Cloud Deployment Guide
Container Support
Docker
How to run the OneDrive client in a Docker container. Please read the Docker Guide
Podman
How to run the OneDrive client with Podman. Please read the Podman Guide
Basic Troubleshooting Steps
If you encounter any issues running the application, please follow these steps before* raising a bug report:
- Check the application version*
Run onedrive --version to confirm which version you are using.
- Ensure you are running the latest release.
- If you are already on the latest release but still experiencing issues, manually build the client from the
masterbranch to test against the very latest code. This includes fixes for bugs discovered since the last tagged release. - If you are using Docker or Podman, ensure you are using the 'edge' Docker Tag. Do not use the 'latest' Docker Tag.
- Run in verbose mode*
Use the --verbose option to provide greater clarity and detailed logging about the issue you are facing.
If you are using Docker or Podman, use the ONEDRIVE_VERBOSE environment variable to increase logging verbosity.
- Test with IPv4 only*
Configure the application to use IPv4 network connectivity only*, then retest. See the 'ip_protocol_version' option documentation for assistance.
- Test with HTTP/1.1 and IPv4*
Configure the application to use HTTP/1.1 over IPv4 only*, then retest. See the 'force_http_11' option documentation for assistance.
- Verify cURL and libcurl versions*
If the above steps do not resolve your issue, upgrade both curl and libcurl to the latest versions provided by the curl developers.
- See Compatibility with curl for details on curl bugs that impact this client.
- Refer to the official cURL Releases page for version information.
- Perform a --resync*
In some cases, a --resync is needed to ensure your data is correctly synced. This option instructs the client to delete its local state database and fully rebuild it from the current online OneDrive contents. This is a powerful recovery and re-alignment action that should be used sparingly and with care.
- See Performing a --resync for further details.
- Open a new issue*
If the problem persists after completing the steps above, proceed to Reporting an Issue or Bug* below and open a new issue with the requested details and logs.
Reporting an Issue or Bug
> [!IMPORTANT]
> Please ensure the problem is a software bug. For installation issues, distribution package/version questions, or dependency problems, start a Discussion instead of filing a bug report.
If you encounter a bug, you can report it on GitHub. Before opening a new issue report:
- Complete the Basic Troubleshooting Steps*
Confirm you’ve run through all steps in the section above.
- Search existing issues*
Check both Open and Closed issues for a similar problem to avoid duplicates.
- Use the issue template*
Open a new bug report using the issue template and fill in all fields*. Complete detail helps us reproduce your environment and replicate the issue.
- Generate a debug log*
Follow this process to create a debug log.
- If you are concerned about personal or business sensitive data in the debug log, you may:
- Create a new OneDrive account, configure the client to use it, use dummy* data to simulate your environment, and reproduce the issue; or
- Provide an NDA or confidentiality agreement for signature prior to sharing sensitive logs.
- Share the debug log securely*
- Do not post debug logs publicly.* Debug logs can include sensitive details (file paths, filenames, API endpoints, environment info, etc.).
- Send the log via email to support@mynas.com.au using a trusted email account.
- Archive and password-protect* the log before sending (e.g.
.zipwith AES or.7z): - Example (zip with password):
zip -e onedrive-debug.zip onedrive-debug.log - Example (7z with password):
7z a -p onedrive-debug.7z onedrive-debug.log - Send the password out-of-band (OOB) — not in the same email as the archive. Email support@mynas.com.au to arrange an OOB method (e.g. separate email thread, phone/SMS, or agreed channel).
- If you require an NDA*, attach your NDA or confidentiality agreement to your email. It will be reviewed and signed prior to exchanging sensitive data.
What to include in your bug report
When raising a new bug report, please include all details requested in the issue template*, such as:
- A clear description of the problem and how to reproduce it
- Your operating system and installation method
- OneDrive account type and client version
- Application configuration and cURL version
- Sync directory location, system mount points, and partition types
- A full debug log, shared securely as described above
Providing complete information makes it much easier to understand, reproduce, and resolve your issue quickly.
> [!NOTE]
> Submitting a bug report starts a collaboration. To help us help you, please:
> - Stay available to answer questions or provide clarifications if needed
> - Test and confirm fixes in your own environment when a pull request (PR) is created for your issue
> [!TIP]
> Reports with missing details are much harder to investigate. Sharing as much as you can up front gives the best chance of a fast and accurate fix.
Known issues
Lists common limitations, known problems, diagnostics, and workarounds. Please read the Known Issues Advice
