Radarr: update is failing (version `GLIBC_2.27&#39; not found) #8893

Author

Owner

@bakerboy448 commented on GitHub (May 1, 2025):

The plan is to move to dotnet 8 in the near future. Which I believe also comes with platform support changes. Cc @mynameisbogdan for additional commentary

@bakerboy448 commented on GitHub (May 1, 2025): The plan is to move to dotnet 8 in the near future. Which I believe also comes with platform support changes. Cc @mynameisbogdan for additional commentary

deekerman commented

Author

Owner

@mynameisbogdan commented on GitHub (May 1, 2025):

Sadly currently there aren't any builds ready for #10258, I'll leave a message when one is ready.

@mynameisbogdan commented on GitHub (May 1, 2025): - Sadly currently there aren't any builds ready for #10258, I'll leave a message when one is ready.

deekerman commented

https://radarr.servarr.com/v1/update/net80/updatefile?os=linux&runtime=netcore&arch=x64
https://radarr.servarr.com/v1/update/net80/updatefile?os=linuxmusl&runtime=netcore&arch=x64
https://radarr.servarr.com/v1/update/net80/updatefile?os=linux&runtime=netcore&arch=arm
https://radarr.servarr.com/v1/update/net80/updatefile?os=linux&runtime=netcore&arch=arm64

Author

Owner

@mynameisbogdan commented on GitHub (May 10, 2025):

Here's a .NET 8 build.

docker pull ghcr.io/linuxserver-labs/prarr:radarr-net80

@mynameisbogdan commented on GitHub (May 10, 2025): Here's a .NET 8 build. https://radarr.servarr.com/v1/update/net80/updatefile?os=linux&runtime=netcore&arch=x64 https://radarr.servarr.com/v1/update/net80/updatefile?os=linuxmusl&runtime=netcore&arch=x64 https://radarr.servarr.com/v1/update/net80/updatefile?os=linux&runtime=netcore&arch=arm https://radarr.servarr.com/v1/update/net80/updatefile?os=linux&runtime=netcore&arch=arm64 `docker pull ghcr.io/linuxserver-labs/prarr:radarr-net80`

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 10, 2025):

@mynameisbogdan, really appreciate this. I've gone ahead and packaged it for Synology as a pre-release. I've deployed on my system as a test and it works well:

Now awaiting the target users on ARMv7 to provide feedback.

@mreid-tt commented on GitHub (May 10, 2025): @mynameisbogdan, really appreciate this. I've gone ahead and packaged it for Synology as a [pre-release](https://github.com/mreid-tt/spksrc/releases/tag/radarr_v6-develop). I've deployed on my system as a test and it works well: <img width="498" alt="Image" src="https://github.com/user-attachments/assets/476321f3-9967-4e48-8eea-b1395d639642" /> Now awaiting the target users on ARMv7 to provide feedback.

deekerman commented

https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linux&runtime=netcore&arch=x64
https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linuxmusl&runtime=netcore&arch=x64
https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linux&runtime=netcore&arch=arm
https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linux&runtime=netcore&arch=arm64

Author

Owner

@mynameisbogdan commented on GitHub (May 10, 2025):

New links for v6:

Keep in mind these builds aren't production ready and they might break something at any time.

@mynameisbogdan commented on GitHub (May 10, 2025): New links for v6: https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linux&runtime=netcore&arch=x64 https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linuxmusl&runtime=netcore&arch=x64 https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linux&runtime=netcore&arch=arm https://radarr.servarr.com/v1/update/v6-develop/updatefile?os=linux&runtime=netcore&arch=arm64 Keep in mind these builds aren't production ready and they might break something at any time.

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 14, 2025):

Hey @mynameisbogdan, the last test version you provided worked successfully on the Synology ARMv7 platform. This looks like a viable path forward to ensure future updates reach those users.

@mreid-tt commented on GitHub (May 14, 2025): Hey @mynameisbogdan, the last test version you provided worked successfully on the Synology ARMv7 platform. This looks like a viable path forward to ensure future updates reach those users.

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 14, 2025):

Hey @mynameisbogdan, do you think we can go ahead and close the upstream ticket at this point? The Microsoft team has requested closure.

@mreid-tt commented on GitHub (May 14, 2025): Hey @mynameisbogdan, do you think we can go ahead and close the upstream ticket at this point? The Microsoft team has requested closure.

deekerman commented

Author

Owner

@mynameisbogdan commented on GitHub (May 14, 2025):

You can since it's all good on .NET 8, but I'm not seeing a Radarr 6 stable till next year.

@mynameisbogdan commented on GitHub (May 14, 2025): You can since it's all good on .NET 8, but I'm not seeing a Radarr 6 stable till next year.

deekerman commented

Author

Owner

@woutercoppens commented on GitHub (May 17, 2025):

What is for now the way forward? I uninstall this test version and go back to the old version of synocommunity?

@woutercoppens commented on GitHub (May 17, 2025): What is for now the way forward? I uninstall this test version and go back to the old version of synocommunity?

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 17, 2025):

What is for now the way forward? I uninstall this test version and go back to the old version of synocommunity?

I’d recommend rolling back to the previous SynoCommunity version. That version can’t update past v5.12.2.9335 — any newer release hits this same issue. If you’re comfortable with the Radarr 6 development branch and it’s working fine for you, you could stick with it, but bear in mind it won’t receive updates until the next dev cycle, which could be several months away.

@mynameisbogdan, do you have any other thoughts?

@mreid-tt commented on GitHub (May 17, 2025): > What is for now the way forward? I uninstall this test version and go back to the old version of synocommunity? I’d recommend rolling back to the previous SynoCommunity version. That version can’t update past v5.12.2.9335 — any newer release hits this same issue. If you’re comfortable with the Radarr 6 development branch and it’s working fine for you, you could stick with it, but bear in mind it won’t receive updates until the next dev cycle, which could be several months away. @mynameisbogdan, do you have any other thoughts?

deekerman commented

Author

Owner

@woutercoppens commented on GitHub (May 17, 2025):

In both scenario's I won't receive any updates until Radarr 6 is released?

@woutercoppens commented on GitHub (May 17, 2025): In both scenario's I won't receive any updates until Radarr 6 is released?

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 17, 2025):

In both scenario's I won't receive any updates until Radarr 6 is released?

That's my interpretation of the current state of things. @mynameisbogdan will have to confirm.

@mreid-tt commented on GitHub (May 17, 2025): > In both scenario's I won't receive any updates until Radarr 6 is released? That's my interpretation of the current state of things. @mynameisbogdan will have to confirm.

deekerman commented

https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linux&runtime=netcore&arch=x64
https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linuxmusl&runtime=netcore&arch=x64
https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linux&runtime=netcore&arch=arm
https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linux&runtime=netcore&arch=arm64

Author

Owner

@mynameisbogdan commented on GitHub (May 17, 2025):

I'm willing to maintain some custom builds with a downgrade version of dotnet for Synology if you're interested.

@mynameisbogdan commented on GitHub (May 17, 2025): I'm willing to maintain some custom builds with a downgrade version of dotnet for Synology if you're interested. https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linux&runtime=netcore&arch=x64 https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linuxmusl&runtime=netcore&arch=x64 https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linux&runtime=netcore&arch=arm https://radarr.servarr.com/v1/update/dotnet6-synology/updatefile?os=linux&runtime=netcore&arch=arm64

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 25, 2025):

I'm willing to maintain some custom builds with a downgrade version of dotnet for Synology if you're interested.

I appreciate the effort, but I'm not sure maintaining custom builds is worthwhile. From what I understand, the internal updater will still target the standard releases, which means updates will continue to fail unless we re-release each version to the repository. Historically, we haven’t maintained apps this way, especially since our update cadence doesn’t align with projects that release frequently. Given that, maintaining custom builds solely for ARMv7 users doesn’t seem like a sustainable approach.

@mreid-tt commented on GitHub (May 25, 2025): > I'm willing to maintain some custom builds with a downgrade version of dotnet for Synology if you're interested. I appreciate the effort, but I'm not sure maintaining custom builds is worthwhile. From what I understand, the internal updater will still target the standard releases, which means updates will continue to fail unless we re-release each version to the repository. Historically, we haven’t maintained apps this way, especially since our update cadence doesn’t align with projects that release frequently. Given that, maintaining custom builds solely for ARMv7 users doesn’t seem like a sustainable approach.

deekerman commented

Author

Owner

@woutercoppens commented on GitHub (May 26, 2025):

I agree that custom builds are not a sustainable approach, but the alternative is that ARMv7 users stay on a release from oct 24.
Some updates via custom builds are better then no updates.

@woutercoppens commented on GitHub (May 26, 2025): I agree that custom builds are not a sustainable approach, but the alternative is that ARMv7 users stay on a release from oct 24. Some updates via custom builds are better then no updates.

deekerman commented

Author

Owner

@mynameisbogdan commented on GitHub (May 28, 2025):

@mreid-tt I failed to ask, but is Radarr the only one with the issue with .NET greater than 6.0.32? I'm curious about Lidarr, Readarr and Prowlarr.

@mynameisbogdan commented on GitHub (May 28, 2025): @mreid-tt I failed to ask, but is Radarr the only one with the issue with .NET greater than 6.0.32? I'm curious about Lidarr, Readarr and Prowlarr.

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 28, 2025):

@mreid-tt I failed to ask, but is Radarr the only one with the issue with .NET greater than 6.0.32? I'm curious about Lidarr, Readarr and Prowlarr.

I believe this affects only the Servarr apps. The Lidarr I use has .NET 6.0.35. I assume so does Readarr and Prowlarr but I don't use these. For the Sonarr I use, they are still at .NET 6.0.13 so not affected.

EDIT: I was only commenting on the .NET versions. I can't say if Lidarr works on ARMv7 as I don't have one of these platforms to test it on. My NAS uses x64.

@mreid-tt commented on GitHub (May 28, 2025): > [@mreid-tt](https://github.com/mreid-tt) I failed to ask, but is Radarr the only one with the issue with .NET greater than 6.0.32? I'm curious about Lidarr, Readarr and Prowlarr. I believe this affects only the Servarr apps. The [Lidarr](https://github.com/Lidarr/Lidarr/blob/7217e891f70f8ff779bb1ca3b789e09ba47088c5/azure-pipelines.yml#L18) I use has .NET 6.0.35. I assume so does [Readarr](https://github.com/Readarr/Readarr/blob/18bca0b228e544cee9eb3c150adb3a8a6c482cae/azure-pipelines.yml#L18) and [Prowlarr](https://github.com/Prowlarr/Prowlarr/blob/c3ee3f2320c6638c6d5aaf88e417ba4f5fe3edd6/azure-pipelines.yml#L18) but I don't use these. For the Sonarr I use, they are still at .NET 6.0.13 so not affected. EDIT: I was only commenting on the .NET versions. I can't say if Lidarr works on ARMv7 as I don't have one of these platforms to test it on. My NAS uses x64.

deekerman commented

2026-02-20 00:08:28 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (May 28, 2025):

To confirm, you're saying Lidarr with 6.0.35 works but Radarr with same version doesn't?

I assume so does Readarr and Prowlarr but I don't use these.

Are they updated to latest versions in the syno repository and zero complains from users?

@mynameisbogdan commented on GitHub (May 28, 2025): To confirm, you're saying Lidarr with 6.0.35 works but Radarr with same version doesn't? > I assume so does [Readarr](https://github.com/Readarr/Readarr/blob/18bca0b228e544cee9eb3c150adb3a8a6c482cae/azure-pipelines.yml#L18) and [Prowlarr](https://github.com/Prowlarr/Prowlarr/blob/c3ee3f2320c6638c6d5aaf88e417ba4f5fe3edd6/azure-pipelines.yml#L18) but I don't use these. Are they updated to latest versions in the syno repository and zero complains from users?

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (May 28, 2025):

@mynameisbogdan Just to clarify, consistent with the issue noted in this ticket, any version built using a .NET runtime newer than 6.0.32 will not work for ARMv7 users. While we don't have direct reports confirming this from users of Lidarr, Readarr, or Prowlarr — likely due to fewer users running these on older platforms — I linked their repositories to show they’re all using the same .NET SDK version, so they’re likely affected in the same way as Radarr.

Regarding the SynoCommunity repository, we don’t publish every new release of the Servarr packages since the internal updaters typically handle incremental updates. However, I’ve published the last versions of each that still use .NET runtime 6.0.32. This ensures that new installs on ARMv7 will at least install and run, although auto-updates to newer versions will fail.

@mreid-tt commented on GitHub (May 28, 2025): @mynameisbogdan Just to clarify, consistent with the issue noted in this ticket, any version built using a .NET runtime newer than 6.0.32 will not work for ARMv7 users. While we don't have direct reports confirming this from users of Lidarr, Readarr, or Prowlarr — likely due to fewer users running these on older platforms — I linked their repositories to show they’re all using the same .NET SDK version, so they’re likely affected in the same way as Radarr. Regarding the SynoCommunity repository, we don’t publish every new release of the Servarr packages since the internal updaters typically handle incremental updates. However, I’ve published the last versions of each that still use .NET runtime 6.0.32. This ensures that new installs on ARMv7 will at least install and run, although auto-updates to newer versions will fail.

deekerman commented

2026-02-20 00:08:28 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (May 28, 2025):

Can anyone post trace logs with the error? I just noticed they are only info.

@mynameisbogdan commented on GitHub (May 28, 2025): Can anyone post trace logs with the error? I just noticed they are only info.

deekerman commented

2026-02-20 00:08:28 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (May 28, 2025):

👋 @woutercoppens, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our troubleshooting guide.

@github-actions[bot] commented on GitHub (May 28, 2025): :wave: @woutercoppens, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our [troubleshooting guide](https://wiki.servarr.com/radarr/troubleshooting#logging-and-log-files).

deekerman commented

Author

Owner

@woutercoppens commented on GitHub (Jun 4, 2025):

Please have a look at https://gist.github.com/woutercoppens/1c61f88f41fc1695350138d0da38dd6d

@woutercoppens commented on GitHub (Jun 4, 2025): Please have a look at https://gist.github.com/woutercoppens/1c61f88f41fc1695350138d0da38dd6d

deekerman commented

Author

Owner

@mreid-tt commented on GitHub (Sep 22, 2025):

I note that in the develop branch we have a pre-release of v6.0.0.10217. This is built with .NET 8 so based on previous testing it should resolve this issue. Let us know @woutercoppens what are your findings with this version.

@mreid-tt commented on GitHub (Sep 22, 2025): I note that in the develop branch we have a pre-release of v[6.0.0.10217](https://github.com/Radarr/Radarr/releases/tag/v6.0.0.10217). This is built with .NET 8 so based on previous testing it should resolve this issue. Let us know @woutercoppens what are your findings with this version.

deekerman commented

Author

Owner

@woutercoppens commented on GitHub (Sep 25, 2025):

How do I install v6.0.0.10217?

I changed the channel to develop (and even restarted Radarr). I can see v6.0.0.10217 in the available updates but when I clikc on install latest, it always downloads v5.28.0.10205.

@woutercoppens commented on GitHub (Sep 25, 2025): How do I install v6.0.0.10217? I changed the channel to develop (and even restarted Radarr). I can see v6.0.0.10217 in the available updates but when I clikc on install latest, it always downloads v5.28.0.10205.

deekerman commented