K1ng0011
-
Posts
30 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by K1ng0011
-
-
This does not fix the problem but I am using it as a work around. Disabling "host access to custom networks" resolves any lockups for me. When I setup vlans I still had the issue. I prefer not to double NAT so I have always set my dockers network type to Host or Custom: br0 with a static IP. I just moved my two dockers that had static IPs to the bridge network type. This gives them a private IP on their own subnet. This allows the qbittorrent docker I have running with open vpn to still work and my other dockers to access qbittorrent. It allows everything to work without "host access to custom networks" from being enabled.
-
Is this the same thing as the global c-stste feature that people disable on AM4 motherboards in the bios?
-
If you look at hoopsters post he reported macvlan call traces in unRAID version 6.5.0 which was released in 2018. This has been an issue for quite a long time. I have seen references that this issue might be related to docker itself and not unRAID but it seems like the issue has not been widespread enough to warrant unRAID reaching out to the people who maintain the docker software. I spent from December 2020 to February 2021 diagnosing this issue on my original motherboard. When I ended up removing my 10 Gig PCIE NIC ASUS XG-C100C from my motherboard the issue stopped. So somehow specific hardware was causing this issue. A the time I was on 6.8.3. Unless there is a wide number of users affected I am not hopeful that this issue will get resolved. Currently I have the "host access to custom networks" setting under my docker container settings page disabled to hopefully prevent any hard lockups to see if unRAID can come up with a solution. If I were you I would install the "CA Backup / Restore Appdata" plugin if you do not have it already. I have had these hard lockups corrupt my app data for my dockers and this allowed me to restore my appdata folder.
-
Looks like others are now having the issue that I have struggled with. I have had the issue with two different motherboards and on versions of unRAID since 6.8.3. I swapped to a motherboard with IPMI and now I have the macvlan issue return. I resolved the issue on my MSI Pro Carbon x370 by removing my 10 gig PCIE NIC and using the onboard NIC. All of my dockers are currently in host mode or br0.2 with a static IP. I had six days of uptime and then just this morning I had another macvlan call trace come up. Since I installed my new motherboard in I check my logs every morning before I go to work and usually after I get off work. It seems like this has been an issue for a long time but something changed and caused more users to be affected than before.
Current Unraid Version: 6.9.2
Original Motherboard: MSI Pro Carbon X370
Current Motherboard: ASRockRack X470D4U2-2T
-
1
-
6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)
in Stable Releases
Posted
11 days and 6 hours of uptime with host access to custom networks disabled. unRAID 6.9.2.