-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] In 4.0.6: Failed to create CoreCLR, HRESULT: 0x80004005 #297
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
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 |
Our smoke tests seem ok for both platforms: https://ci-tests.linuxserver.io/linuxserver/sonarr/latest/index.html |
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 Maybe you can run your smoke test on the actual |
https://ci-tests.linuxserver.io/linuxserver/sonarr/4.0.6.1805-ls244/index.html |
I used |
Is there an existing issue for this?
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:
Steps To Reproduce
A downgrade to 4.0.5 recovers so it must be something that changed from 4.0.5 to 4.0.6
Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: