Mount Wasabi on Linux — NetDrive's Experimental Ubuntu Build

A build server running Ubuntu needs to read release archives out of a Wasabi bucket every night, and downloading the whole bucket with a CLI tool before each job wastes minutes the pipeline doesn’t have. NetDrive’s Linux build mounts that Wasabi bucket at a regular mount point, so a script reading /mnt/wasabi/releases/latest.tar.gz just sees the current file — no separate sync step, no pre-job download.

Mount Wasabi on Ubuntu

NetDrive lets Google Drive, OneDrive, S3, SFTP, WebDAV and more appear as native drives on Windows and macOS — no syncing, no full downloads.

• Runs on Ubuntu 16.04 and later
• Mounts your Wasabi bucket at a Linux mount point — no separate sync folder
• The same Wasabi credentials work across Windows, macOS, and Linux

WindowsmacOS

Download NetDrive for Linux →

Free trial. Lifetime and subscription plans available.

Wasabi on NetDrive’s Linux Build

NetDrive has supported S3-compatible storage since version 3.4.398 (March 2018), and Wasabi — with no egress fees and no API request fees — is one of the explicitly listed S3-compatible providers. On Windows and macOS that support is treated as production-grade. On Linux, it inherits NetDrive’s own experimental label, a designation that applies to the entire Linux build rather than to any single provider. The current NetDrive release across all platforms is 3.19.7.

NetDrive for Linux isn’t distributed through apt or a distro package manager. It ships as a GitHub release at github.com/NetDrive/installer, and Ubuntu 16.04 is the minimum supported version.

Installing NetDrive on Ubuntu

1. Go to github.com/NetDrive/installer and download the release that matches your Ubuntu version.
2. Follow the release notes bundled with that build — a driver component needs to install before NetDrive can mount anything, and the process may prompt for sudo.
3. Install the NetDrive package.
4. Launch NetDrive from a terminal or your desktop environment’s application menu.

Because Linux builds ship as GitHub releases instead of through apt upgrade, this platform is maintained on its own release schedule — a fix that lands for Windows or macOS this week isn’t guaranteed to reach Linux the same week. Worth knowing if a scheduled job depends on specific NetDrive behavior.

Gathering Wasabi Credentials

Before opening NetDrive, collect three values from the Wasabi console:

• Access Key ID — generated under Account → Access Keys.
• Secret Access Key — shown once at creation time. If you’ve lost it, generate a new key pair.
• Regional endpoint URL — Wasabi uses region-specific hostnames. A bucket in us-east-1 uses s3.wasabisys.com; eu-central-1 uses s3.eu-central-1.wasabisys.com. Wasabi’s service endpoint documentation lists every region hostname.

Step-by-Step: Connect Your Wasabi Bucket

1. Open NetDrive’s Drive Manager and click + Add Drive.
2. Select Amazon S3 from the list of connection types — Wasabi is S3-compatible, so this is the correct connector rather than a separate “Wasabi” entry.
3. Access Key / Secret Key — paste the credentials from the Wasabi console.
4. Custom endpoint — enable the “Use custom endpoint” toggle and enter your bucket’s regional hostname, for example s3.eu-central-1.wasabisys.com.
5. Bucket — type the bucket name, or use the list function to enumerate buckets associated with your credentials.
6. Mount point — a path like /mnt/wasabi, or any empty directory your user account can write to.
7. Click Connect. NetDrive authenticates against Wasabi and mounts the bucket at that path.

Verifying the Mount

Check the mount from a terminal rather than relying on a file manager alone, particularly on an experimental build:

# Confirm the mount is listed
mount | grep wasabi

# Or just try listing it
ls /mnt/wasabi

Mount point stays empty after Connect — check that the directory exists and is writable by the user running NetDrive. An unwritable or missing mount point is the most common cause of a silent failure on Linux.

403 or authentication errors — double-check the regional endpoint hostname against your bucket’s actual region. Wasabi rejects requests sent to the wrong regional endpoint even when the access key and secret are correct.

Large buckets take a while to list the first time — the Linux build streams directory listings the same way Windows and macOS do; a bucket with tens of thousands of objects can take a moment to populate on first browse, even though Wasabi itself responds quickly.

Wrap-up

Mounting Wasabi on Ubuntu brings the same drive-style access NetDrive offers on Windows and macOS to a Linux build server or workstation, through an installer distributed on GitHub rather than a package repository. For the broader Linux picture, see NetDrive on Ubuntu Linux; for the same provider on a more heavily tested platform, see Mount Wasabi on Windows with NetDrive; and if you hit access errors after connecting, Fix S3 Access Denied Errors with NetDrive covers the credential and policy checks that apply equally to Wasabi’s S3-compatible API.

— Jay, NetDrive