joshstrange Posted August 28, 2015 Share Posted August 28, 2015 Let me start off by saying I am loving docker in unRaid 6 and I am using it heavily. I am currently having a problem with one of my containers which I *think* is related to a bug in the docker image kernel (https://forums.sonarr.tv/t/native-mono-crashes-kernel-fix-released/4985/136). If I understand correctly containers share the host kernel and so the bug must exist in the docker image that all the containers run in. How would I go about checking what version of kernel it is running and updating it if it turns out that is the culprit. I've done a ton of searching both on google and these forums but I've come up with nothing. Am I crazy or is this possible? Link to comment
jonp Posted August 28, 2015 Share Posted August 28, 2015 Docker doenst have a kernel independent of the host. I'm sorry to say that until that fix makes it into a host kernel we add to unRAID, this issue may persist with that container. Good news is we are staying pretty current as far as kernels go, so as new ones are available, we tend to upgrade pretty quickly. Not sure how long till the fix is in. Keep in mind, I didn't review this specific link. If you can find out what kernel version will get the fix, I can give you at least a rough idea of how long it'll take to get there. Link to comment
BRiT Posted August 29, 2015 Share Posted August 29, 2015 Seems like a fix was in older kernels but newer ones have oddities in 4.1.x interacting with mono due to GCC inline issues. https://forums.sonarr.tv/t/native-mono-crash-on-linux-kernel-4-1-2/6330 Link to comment
jonp Posted August 29, 2015 Share Posted August 29, 2015 Seems like a fix was in older kernels but newer ones have oddities in 4.1.x interacting with mono due to GCC inline issues. https://forums.sonarr.tv/t/native-mono-crash-on-linux-kernel-4-1-2/6330 Thanks for the link there. The sonarr guys seem a little put off by folks even bringing it up it seems (probably tired of having folks getting too far ahead of their tested / supported environment). Bottom line, its not going to work in our kernel. I would advise folks that need this app to run it in a VM, along with any other apps that have kernel compatibility issues. Most docker containers shouldn't have a problem based on kernel versions, but those that do should be moved to VMs or an alternative option should be considered. Link to comment
joshstrange Posted August 29, 2015 Author Share Posted August 29, 2015 Thank you very much for the suggestion and proposed fix. I guess I'm just going to have to run Sonarr in my debian VM instead of trying to get the docker container to work. Also thank you for informing me that docker image and unraid host OS share the same kernel as I did not know that before! Link to comment
CHBMB Posted August 29, 2015 Share Posted August 29, 2015 I'm using Sonarr without issue and have been since the V6 beta 11 I think... You sure this is a problem with the kernel and not some other issue? I reckon if Sonarr had an issue running as a docker container in Unraid then a lot more people would be mentioning it. EDIT: And Unraid is way ahead of the kernels they're talking about in that thread. We're on 4.1.5 on RC6, and V6.0.1 was 4 something too. Link to comment
deadsoulz Posted August 30, 2015 Share Posted August 30, 2015 I have had 0 problems with Sonarr as well. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.