Skip to content

Deployrr install errors: root user, sudo and architecture

TroubleshootingDeployrr v6.0+CurrentInstallHost system

You see one of these messages when you install or start Deployrr.

When you start Deployrr:

[ERROR] Do not run Deployrr as the root user. Run as a regular user with sudo privileges instead.

When you run the curl installer without sudo:

This installer must be run as root. Try: sudo bash -c "$(curl -fsSL https://files.deployrr.app/install.sh)"

When you run the npx installer without sudo:

This installer requires root privileges.
Run: sudo npx @simplehomelab/deployrr

When the installer does not support your processor:

Unsupported architecture: <arch>. Deployrr supports x86_64 and ARM64.

The npx installer prints Unsupported architecture: <arch> instead.

Other messages from the installers:

Required command not found: curl
Required command not found: tar
Failed to download binary
Download failed. Check your internet connection.

Other errors you may see around the install:

NAME is not in the sudoers file
sudo: npx: command not found
deployrr: command not found
Could not create link in /usr/local/bin. You may need to run via absolute path.

The installer and Deployrr have opposite rules about root.

  • You run the installer with sudo, because it needs root rights.
  • You start Deployrr as a regular user, without sudo. Deployrr asks for your sudo password when it needs root.

Most other errors come from a CPU that is not supported, a missing tool, or a network problem.

Find your message below.

“Do not run Deployrr as the root user”

Section titled ““Do not run Deployrr as the root user””

You are logged in as root, or you started Deployrr with sudo. You need a regular user that can use sudo.

  1. Check who you are:

    Terminal window
    whoami

    If it prints root, create a regular user in the next section. If it prints another name, go to step 3.

  2. Log in as that regular user. If you connect over SSH, open a new SSH session with that user name. See SSH access.

  3. Start Deployrr without sudo:

    Terminal window
    deployrr
  4. Enter your password when Deployrr asks for it.

On a new VPS, also set up SSH keys and a firewall for this user. See Secure a fresh VPS before you install Deployrr.

Use NAME as the user name you want. Replace NAME in every command. If you are logged in as root, you can leave out sudo.

To see this done on Ubuntu, watch Docker on Proxmox LXC: creating a non-root user with sudo at 10:20. For the written steps, read UDMS part 05: create a new user (manual setup).

  1. Create the user and set a password when asked:

    Terminal window
    sudo adduser NAME

    On Fedora and RHEL, adduser does not ask for a password. Set one with sudo passwd NAME.

  2. Add the user to the sudo group:

    Terminal window
    sudo usermod -aG sudo NAME

    On Fedora and RHEL, the group is called wheel:

    Terminal window
    sudo usermod -aG wheel NAME
  3. Log out, then log in again as NAME. The new group does not apply until you do. You can also switch to the user in the same session with su - NAME.

  4. Check that sudo works:

    Terminal window
    sudo -v

    It asks for your password and prints nothing else when it works.

  5. Check that the group is listed:

    Terminal window
    groups

If sudo says NAME is not in the sudoers file, the user is not in the group yet. Repeat step 2 from an account that has sudo rights, then log in again as NAME.

“This installer must be run as root” or “This installer requires root privileges”

Section titled ““This installer must be run as root” or “This installer requires root privileges””

You ran the installer without sudo. Run the install command again with sudo, exactly as shown in Install Deployrr.

The two commands are:

Terminal window
sudo npx @simplehomelab/deployrr@latest
Terminal window
sudo bash -c "$(curl -fsSL https://files.deployrr.app/install.sh)"

“Required command not found: curl” or “tar”

Section titled ““Required command not found: curl” or “tar””
  1. Install both tools. On Debian and Ubuntu:

    Terminal window
    sudo apt install curl tar
  2. Run the curl installer again.

The npx method needs Node.js and npm, and your server does not have them. Use the curl installer instead. See Install Deployrr.

Deployrr supports 64-bit x86_64 and 64-bit ARM64 processors. It does not support 32-bit ARM (armv7l, armhf) or i686. A Raspberry Pi running 32-bit Raspberry Pi OS is one example.

  1. Check your processor type:

    Terminal window
    uname -m
  2. If it prints x86_64 or aarch64, you are on a supported processor. Run the installer again and check for typing mistakes.

  3. If it prints anything else, install a 64-bit version of your operating system. Then install Deployrr again.

On a Raspberry Pi 4 or 5, 32-bit Raspberry Pi OS can start a 64-bit kernel. Then uname -m prints aarch64 and the installer goes ahead, even though the rest of the system is 32-bit. Before you install on a Raspberry Pi, also run:

Terminal window
dpkg --print-architecture

It must print arm64. If it prints armhf, install 64-bit Raspberry Pi OS, then install Deployrr.

After this message, /opt/deployrr/apps may already exist even though Deployrr is not installed. It does no harm.

“Failed to download binary” or “Download failed”

Section titled ““Failed to download binary” or “Download failed””

The installer could not download Deployrr.

  1. Check that your server can reach the internet.
  2. Run the install command again.
  3. If it keeps failing, check your DNS and firewall settings.

The npx installer also prints Download failed when curl is missing. If your server has internet, install curl and try again.

The installer normally makes deployrr available from any folder. The curl installer prints Could not create link in /usr/local/bin. You may need to run via absolute path. when it cannot. The npx installer prints the full path to use instead, after Run:.

  1. List the install folder to see the file name:

    Terminal window
    ls /opt/deployrr
  2. Start Deployrr with the full path. Replace FILE_NAME with the deployrr_v*.app file you saw. Do not use sudo.

    Terminal window
    /opt/deployrr/FILE_NAME

Run the installer again when the Deployrr program is missing or damaged. For example, after Settings > Reset the deployrr command points to a missing file, or you deleted a file in /opt/deployrr by mistake.

Running the installer again is safe:

  • It downloads the Deployrr program again and points the deployrr command at it.
  • It does not delete anything, so your saved settings, setup status and logs in /opt/deployrr stay.
  • It does not touch your Docker folder, your apps or your running containers.
  • The npx installer also copies the app files into /opt/deployrr/apps again, replacing the files with the same name.
  1. Run your install command again with sudo. See Run the installer again.

    If Deployrr still starts, deployrr update does the same. It shows the method you used last (npx or curl) as Install Method:. When you are already on the latest version, it asks Would you like to force reinstall Deployrr anyway? (y/N). Type y.

  2. Start Deployrr without sudo:

    Terminal window
    deployrr
  3. If an app install stops with App 'NAME' not found, get the app files back. Build Cache needs Disclaimers done first. Open Prerequisites > Build Cache and choose Yes in the Build App Cache box. Apps > Refresh Cache does the same. Wait for Building app registry... to finish, then install the app again.

A Reset deletes the Deployrr program, so run the installer again before you start Deployrr. Some Prerequisites steps also need to be done again. See Refresh, Reset or Remove Deployrr.

  1. Run whoami. It prints your regular user name, not root.
  2. Run deployrr. The Deployrr main menu opens with Prerequisites as the first item.

Next, follow Quick start to finish setup. To keep Deployrr current later, see Update Deployrr.