Lingarr

[MickLesk]

Name of the Script

Lingarr

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 supported

📋 Script Details

Lingarr translates subtitles in Radarr/Sonarr libraries — either through a self-hosted LibreTranslate or a hosted provider (DeepL, OpenAI, Anthropic, Gemini). Requested in discussion #3442.

Unlike Shoko, this one really does need the SDK. I checked whether the release ships a framework-dependent build like Shoko does — it does not: 1.2.4 has no assets at all, and Lingarr.Server/Dockerfile builds with mcr.microsoft.com/dotnet/sdk:10.0.

• .NET 10 is not in Debian trixie (only 8 is), so the Microsoft repository is added via packages-microsoft-prod.deb for $(get_os_info version_id), then dotnet-sdk-10.0.
• Two-stage build, mirroring the Dockerfile: Node 24 builds Lingarr.Client and the result is copied to Lingarr.Server/wwwroot, then dotnet publish -c Release /p:UseAppHost=false produces /opt/lingarr_app, started with dotnet Lingarr.Server.dll.
• Build output goes to /opt/lingarr_app rather than into the source tree, so CLEAN_INSTALL on update only wipes the sources.
• PostgreSQL via DB_CONNECTION=postgresql; upstream also supports MySQL and SQLite.
• Note: the default SERVICE_TYPE=libretranslate points at a LIBRE_TRANSLATE_URL that does not exist yet — a backend must be configured before it does anything. Flagged as the first warning.
• Note: Lingarr writes subtitle files next to the media, so the mounted library paths need write access.

Source: https://github.com/lingarr-translate/lingarr

[github-actions]

The Lingarr script is ready for testing:

bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/lingarr.sh)"

Set a translation backend in /opt/lingarr.env before use. The default points at a LibreTranslate instance that does not exist yet - either deploy one and set LIBRE_TRANSLATE_URL, or switch SERVICE_TYPE to a hosted provider and add its API key.
Mount your media libraries into the LXC and connect Radarr/Sonarr through the web UI. Lingarr writes subtitle files next to the media, so it needs write access to those paths.
Needs the .NET 10 SDK, which Debian does not ship - it comes from the Microsoft repository. The build is therefore large; the compiled output lands in /opt/lingarr_app while the source tree stays in /opt/lingarr.
Metadata is stored in the local PostgreSQL database 'lingarr'. Upstream also supports MySQL and SQLite via DB_CONNECTION.

Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

Discord testing thread: https://discord.com/channels/1302816934508630047/1534106612246253718