You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
True issue - the Auto Disc Ripper is dependent on makemkvcon which periodically requires network connectivity to the mothership for updates. When there is no internet and it's time to check for updates this is a blocking action and prevents makemkvcon from returning and thereby breaks anything dependent on it.
User based solutions:
Get your internet back online / allow the container to get to the internet.
Set app_UpdateEnable = "0" in settings.conf in /config and restart the container.
Recommendation:
Add an environmental variable that configures app_UpdateEnable when the container is stood up. This will help with headless installs and anyone that has crappy internet
Risks of implementing the recommendation:
While MakeMKV is able to run without internet connectivity, the updating is there for a reason. Turing it off and pulling a new container when one is released may leave things in an outdated state. Recommend that if an environmental variable is created that it be defaulted to 1/On so that the user needs to make a conscious decision understanding the risks of turning off this setting.
Lastly - I wonder if this may account for other weirdness with the autodiscripper reported here. Wondering if turning it off may make some other problems go away. A blocking process can break tons of downstream things. When mine broke, it broke in stages and progressively got worse. Once I configured that setting everything came back.
The text was updated successfully, but these errors were encountered:
Idea
See #183 (comment)
True issue - the Auto Disc Ripper is dependent on makemkvcon which periodically requires network connectivity to the mothership for updates. When there is no internet and it's time to check for updates this is a blocking action and prevents makemkvcon from returning and thereby breaks anything dependent on it.
User based solutions:
Recommendation:
Risks of implementing the recommendation:
While MakeMKV is able to run without internet connectivity, the updating is there for a reason. Turing it off and pulling a new container when one is released may leave things in an outdated state. Recommend that if an environmental variable is created that it be defaulted to 1/On so that the user needs to make a conscious decision understanding the risks of turning off this setting.
Lastly - I wonder if this may account for other weirdness with the autodiscripper reported here. Wondering if turning it off may make some other problems go away. A blocking process can break tons of downstream things. When mine broke, it broke in stages and progressively got worse. Once I configured that setting everything came back.
The text was updated successfully, but these errors were encountered: