[BUG] In 4.0.6: Failed to create CoreCLR, HRESULT: 0x80004005

ccMatrix commented 4 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

After updating from sonarr 4.0.5 to sonarr 4.0.6, sonarr does not run anymore. Container shows as running in portainer but does not listen on the port or initialize correctly. It just runs into the error message and never recovers.

Expected Behavior

Sonarr starts and listens on port 8989. Expected output from version 4.0.5.1710-ls243:


To support the app dev(s) visit:
Sonarr: https://sonarr.tv/donate
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 4.0.5.1710-ls243
Build-date: 2024-06-28T23:33:24+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr - Version 4.0.5.1710 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Debug] Bootstrap: Console selected 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Debug] Microsoft.Extensions.Hosting.Internal.Host: Hosting starting 
[Info] AppFolderInfo: Data directory is being overridden to [/config] 
[Info] MigrationController: *** Migrating data source=/config/sonarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating 
[Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation  
[Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation 
[Info] DatabaseEngineVersionCheck: SQLite 3.45.3 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.2299563s 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.2420174s 
[Info] MigrationController: *** Migrating data source=/config/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrating 
[Info] FluentMigrator.Runner.MigrationRunner: PerformDBOperation  
[Info] NzbDrone.Core.Datastore.Migration.Framework.NzbDroneSQLiteProcessor: Performing DB Operation 
[Info] DatabaseEngineVersionCheck: SQLite 3.45.3 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.0045732s 
[Info] FluentMigrator.Runner.MigrationRunner: DatabaseEngineVersionCheck migrated 
[Info] FluentMigrator.Runner.MigrationRunner: => 0.005266s 
[Info] Microsoft.Hosting.Lifetime: Now listening on: http://[::]:8989 
[ls.io-init] done.
[Info] Microsoft.Hosting.Lifetime: Application started. Press Ctrl+C to shut down. 
[Info] Microsoft.Hosting.Lifetime: Hosting environment: Production 
[Info] Microsoft.Hosting.Lifetime: Content root path: /app/sonarr/bin 
[Info] ManagedHttpDispatcher: IPv4 is available: True, IPv6 will be disabled

Steps To Reproduce

Install sonarr 4.0.5 on Raspberry Pi 4 via e.g. portainer
Connect to port 8989 and see webinterface
Update to 4.0.6
Webinterface is not shown and container doesn't start anymore.

A downgrade to 4.0.5 recovers so it must be something that changed from 4.0.5 to 4.0.6

Environment

- OS:Ubuntu 22.04 LTS
- Docker 26.1.4 installed via apt from official repo `https://download.docker.com/linux/ubuntu`
- System is a Raspberry Pi 4 running aarch64: `Linux ubuntu 5.15.0-1055-raspi #58-Ubuntu SMP PREEMPT Sat May 4 03:52:40 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux`

CPU architecture

arm64

Docker creation

Docker created via Portainer Web UI.

Name: sonarr
Image: lscr.io/linuxserver/sonarr:4.0.6
Port mapping: 8989 -> 8989
Volumes:
  /tv -> /media/tvshows (host)
  /config -> Sonarr-Config - local (volume)
  /downloads -> /data/downloads (host)
Env:
  PUID: 1000
  PGID: 1000
  TZ: Europe/Berlin
Restart Policy: Unless stopped
Network:
  Network: media
  Hostname: sonarr

Container logs

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Sonarr: https://sonarr.tv/donate

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 4.0.6.1805-ls244
Build-date: 2024-07-02T04:35:47+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005
Failed to create CoreCLR, HRESULT: 0x80004005

github-actions[bot] commented 4 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

ccMatrix commented 4 months ago

It looks like all the latest versions of the *arr containers have the same issue. Tested Sonarr, Radarr, Readarr and Lidarr. All have the same error on the latest release. They all have in common that they were updated to use the base image ghcr.io/linuxserver/baseimage-alpine:3.20 instead of ghcr.io/linuxserver/baseimage-alpine:3.19. So it is possible the error is in the baseimage

j0nnymoe commented 4 months ago

Our smoke tests seem ok for both platforms: https://ci-tests.linuxserver.io/linuxserver/sonarr/latest/index.html We don't support portainer for container deployment, could you try with true compose please?

ccMatrix commented 4 months ago

Doesn't matter if I run it manually, via docker compose or Portainer. Same results.

Why is your smoke test for 4.0.5 listed as the latest when your docker hub tag for latest is 4.0.6. How can latest which is supposed to be stable be higher than develop?

Maybe you can run your smoke test on the actual latest tag instead of the 4.0.5. should show the same result then. I can confirm that 4.0.5 works.

j0nnymoe commented 4 months ago

https://ci-tests.linuxserver.io/linuxserver/sonarr/4.0.6.1805-ls244/index.html Looks to work - latest was a dev build as it's the most recent build.

ccMatrix commented 4 months ago

I used docker system prune -a to delete all remains of the new tag from the system, then updated the container to the latest and that worked. Looks like a build step or image was corrupted by a faulty hard disk resulting in a bad local image. It works now. Thanks for your help!

linuxserver / docker-sonarr