Starting navidrome.service fails with code=exited, status=203/EXEC

[BeanieBarrow]

Hi all!

I tried to set up Navidrome on my Raspberry Pi 3 B+ (arm64 architecture). I downloaded the tarball from the releases page (navidrome_0.49.3_Linux_arm64.tar.gz), ran the commands on the Linux Install page. The tarball got uncompressed to /opt/navidrome with user:group navidrome:navidrome, then I copied the music/ folder to the root directory with the same ownerships.

Running the three systemd-related commands on the bottom returns the following:

● navidrome.service - Navidrome Music Server and Streamer compatible with Subsonic/Airsonic
     Loaded: loaded (/etc/systemd/system/navidrome.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2023-06-04 07:31:00 CEST; 316ms ago
    Process: 27388 ExecStart=/opt/navidrome/navidrome --configfile /var/lib/navidrome/navidrome.toml (code=exited, status=203/EXEC)
   Main PID: 27388 (code=exited, status=203/EXEC)
        CPU: 92ms

Jun 04 07:31:00 raspberrypi systemd[1]: navidrome.service: Scheduled restart job, restart counter is at 5.
Jun 04 07:31:00 raspberrypi systemd[1]: Stopped Navidrome Music Server and Streamer compatible with Subsonic/Airsonic.
Jun 04 07:31:00 raspberrypi systemd[1]: navidrome.service: Start request repeated too quickly.
Jun 04 07:31:00 raspberrypi systemd[1]: navidrome.service: Failed with result 'exit-code'.
Jun 04 07:31:00 raspberrypi systemd[1]: Failed to start Navidrome Music Server and Streamer compatible with Subsonic/Airsonic.

My /etc/systemd/system/navidrome.service:

[Unit]
Description=Navidrome Music Server and Streamer compatible with Subsonic/Airsonic
After=remote-fs.target network.target
AssertPathExists=/var/lib/navidrome

[Install]
WantedBy=multi-user.target

[Service]
User=navidrome
Group=navidrome
Type=simple
ExecStart=/opt/navidrome/navidrome --configfile "/var/lib/navidrome/navidrome.toml"
WorkingDirectory=/var/lib/navidrome
TimeoutStopSec=20
KillMode=process
Restart=on-failure

# See https://www.freedesktop.org/software/systemd/man/systemd.exec.html
DevicePolicy=closed
NoNewPrivileges=yes
PrivateTmp=yes
PrivateUsers=yes
ProtectControlGroups=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6
RestrictNamespaces=yes
RestrictRealtime=yes
SystemCallFilter=~@clock @debug @module @mount @obsolete @reboot @setuid @swap
ReadWritePaths=/var/lib/navidrome

# You can uncomment the following line if you're not using the jukebox This
# will prevent navidrome from accessing any real (physical) devices
#PrivateDevices=yes

# You can change the following line to `strict` instead of `full` if you don't
# want navidrome to be able to write anything on your filesystem outside of
# /var/lib/navidrome.
ProtectSystem=strict

# You can uncomment the following line if you don't have any media in /home/*.
# This will prevent navidrome from ever reading/writing anything there.
#ProtectHome=true

# You can customize some Navidrome config options by setting environment variables here. Ex:
#Environment=ND_BASEURL="/navidrome"

My /var/lib/navidrome/navidrome.toml:

MusicFolder = "/music"

EDIT: I found out that the Raspberry Pi 3 B+ is and ARMv8 processor (taken from the Specification part of its official site). There's only a binary up until ARMv7. Does this mean I can't run Navidrome on my Pi?

[BeanieBarrow]

Ran cat /proc/cpuinfo to find out that my Raspberry Pi 3 B+ actually has an ARMv7 processor. I downloaded it and installed like the steps said.