Failed to create CoreCLR, HRESULT: 0x80070008 #518
Replies: 3 comments 1 reply
-
Googling Failed to create CoreCLR, HRESULT: 0x80070008... https://www.linuxserver.io/blog/anatomy-of-an-issue "Finally, one of the team reported being able to replicate the problem and we started digging into what was special about their setup. After a lot of back and forth and numerous test images being built we finally identified a difference: they were running a very out of date version of Docker. Specifically 19.03.5, which was released 2019-11-14. We know we've had issues in the past with older Docker versions causing problems so we got them to update to latest and retest: everything worked as expected." |
Beta Was this translation helpful? Give feedback.
-
Encountered this on unRAID 6.10 which had Docker v20.10.9. The issue is gone after updating unRAID to 6.11.1 with Docker v20.10.18 |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Affected Version
Latest
Describe the bug
Fatal: Exits.
Volume is, however utilized.
Steps To Reproduce
Steps to reproduce the behaviour:
Reproduction rate
100%
Host System Information (where ispy agent is running/hosted):
Beta Was this translation helpful? Give feedback.
All reactions