I think this is because rpi4 can run arm64 or armhf. You may be able to get around it by specifying the arm64v8 in the tag so it does not use the manifest. If that does not work I would look to the installed docker version
this post was submitted on 23 Aug 2025
19 points (95.2% liked)
Selfhosted
50894 readers
527 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Oh I didn’t realize it could use two different architectures, I can see how that might mess it up, I’ll look in to that thank you.
Make a docker-compose.yml file and paste this into it:
services:
lidarr:
container_name: lidarr
hostname: lidarr
### Use custom docker network
#networks:
# - CustomNetworkName
ports:
- 8686:8686
image: lscr.io/linuxserver/lidarr:arm64v8-latest
restart: unless-stopped
volumes:
- /path/to/lidarr/config:/config
- /path/to/music:/music #optional
- /path/to/downloads:/downloads #optional
environment:
- PGID=1000
- PUID=1000
healthcheck:
test: curl --fail localhost:8686 || exit 1
interval: 60s
retries: 5
start_period: 300s
timeout: 2s
This should work for you, just change the volume mounts so that they associate with your setup and run sudo docker compose up -d to start the container, sudo docker compose down to bring it down.
LSIO documentation describes the arm64v8-latest tag for their image.
I got the same error even when using the arm64 tag
Something else must be wrong then because I just copied and pasted that onto my raspberry pi and was able to start the container without issue, are you sure you’re using the tag properly?
user@raspberrypi:~/test $ sudo docker compose up
[+] Running 10/10
✔ lidarr Pulled 22.0s
✔ 995f2a46b147 Pull complete 2.7s
✔ e1cde46db0e1 Pull complete 3.1s
✔ acaee427f4c7 Pull complete 3.5s
✔ 255c3937324a Pull complete 4.1s
✔ edec534df16f Pull complete 4.6s
✔ b163a490af0b Pull complete 6.3s
✔ bd4af268fa91 Pull complete 6.8s
✔ ff4dab968553 Pull complete 14.9s
✔ 004112d930a4 Pull complete 15.3s
[+] Running 2/2
✔ Network test_default Created 0.2s
✔ Container lidarr Created 4.0s
Attaching to lidarr
lidarr | [migrations] started
lidarr | [migrations] no migrations found
lidarr | ───────────────────────────────────────
lidarr |
lidarr | ██╗ ███████╗██╗ ██████╗
lidarr | ██║ ██╔════╝██║██╔═══██╗
lidarr | ██║ ███████╗██║██║ ██║
lidarr | ██║ ╚════██║██║██║ ██║
lidarr | ███████╗███████║██║╚██████╔╝
lidarr | ╚══════╝╚══════╝╚═╝ ╚═════╝
lidarr |
lidarr | Brought to you by linuxserver.io
lidarr | ───────────────────────────────────────
lidarr |
lidarr | To support the app dev(s) visit:
lidarr | Lidarr: https://opencollective.com/lidarr
lidarr |
lidarr | To support LSIO projects visit:
lidarr | https://www.linuxserver.io/donate/
lidarr |
lidarr | ───────────────────────────────────────
lidarr | GID/UID
lidarr | ───────────────────────────────────────
lidarr |
lidarr | User UID: 1000
lidarr | User GID: 1000
lidarr | ───────────────────────────────────────
lidarr | Linuxserver.io version: 2.12.4.4658-ls50
lidarr | Build-date: 2025-08-20T02:50:40+00:00
lidarr | ───────────────────────────────────────
lidarr |
lidarr | [custom-init] No custom files found, skipping...
lidarr | [Info] Bootstrap: Starting Lidarr - /app/lidarr/bin/Lidarr - Version 2.12.4.4658
lidarr | [Info] AppFolderInfo: Data directory is being overridden to [/config]
lidarr | [Debug] Bootstrap: Console selected
lidarr | [Info] AppFolderInfo: Data directory is being overridden to [/config]
lidarr | [Info] AppFolderInfo: Data directory is being overridden to [/config]
lidarr | [Warn] Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager: No XML encryptor configured. Key {bff9bf8a-f5db-4092-9ada-c55e886ac294}
I just copy pasted yours into mine and I still got the same error.