glibc Scripted Installer
Many Linux distributions use the GNU Project’s C standard library: 🌐 glibc.
This includes: Debian, Ubuntu, RedHat and their derivatives.
Storj’s Object Mount glibc scripted installer (a .run file) is compatible with all such Linux distributions.
This installer shell script allows you to install Object Mount (for the current user) without needing root privileges — no sudo required.
Follow the steps below to install and configure Object Mount for glibc platforms.
Step 1. Download the Install Script
Download the latest scripted installer.
- Note: If you do not have a download link, reach out to your 🌐 Storj Representative.
The glibc scripted installer is named cuno-<version>-x86_64-glibc-installer.run. The file cuno-<version>-amd64-glibc-installer.run is the same installer under the Debian architecture name; either one works.
- Note: Object Mount for Linux runs on 64-bit Intel and AMD (x86_64) processors. ARM-based processors are not supported at this time.
Step 2. Install & Activate Object Mount
- Note: If you do not yet have a license key, ask your 🌐 Storj Representative for a trial key.
2a. To install Object Mount for use only by the current user, run the following command from a terminal window:
2b. To install Object Mount to be used by all users system-wide, add sudo to the front of the command:
2c. The installation process will prompt you to read and agree to the Object Mount end-user license agreement (EULA).
- Note: You can automate this step by setting the environment variable
CUNO_INSTALL_ACCEPT_EULA="yes". (This is equivalent to accepting the EULA).
2d. The installer then activates Object Mount if the environment variable CUNO_INSTALL_LICENSE is set to your license key or to the full path of a license key file. Set it to none, or leave it unset, to skip activation. With sudo, set CUNO_INSTALL_LICENSE and CUNO_INSTALL_ACCEPT_EULA after sudo (for example sudo CUNO_INSTALL_LICENSE=/path/to/license.txt <install command>); sudo drops variables set before it.
If Object Mount is not activated, the installer prints the next steps. Activate it afterwards with cuno creds activate; see Activate a License Key.
Installation Locations: Scripted Installers
When Object Mount is installed via a Scripted Installer (e.g.: glibc or musl), components are installed to different locations depending on whether it was installed by a root, or by a non-root user.
| Install Method | Install directory | Symlinks created |
|---|---|---|
| Non-Root User | ~/.local/opt/cuno/ | ~/.local/bin/cuno |
~/.local/lib/x86_64-linux-gnu/cuno.so | ||
bash completions in ~/.local/share/bash-completion/completions/ | ||
Root User (sudo) | /opt/cuno/ | /usr/bin/cuno |
/usr/lib/cuno.so | ||
| bash completions in the system bash-completion directory | ||
zsh completions in /usr/share/zsh/vendor-completions/ |
Next Steps
Once Object Mount is installed, proceed to the Linux User Guide article: Validate Functionality & Access Object Storage to ensure you can access both public and private Object Storage buckets.