thecode

Since @bonienl mentioned my config is missing "SYSNICS", renamed the network.cfg file and rebooted the server. This doesn't make any problem since the server IPv4 is also reserved on the router DHCP. After reboot now I noticed two changes: 1. br0 interface metric changed from 1 to 1006 2. broadcast address for br0 changed from 0.0.0.0 to 192.168.x.255 I was already suspecting that having both shim-br0 and br0 using the same metric can cause a problem with routing (thous maybe creating the incomplete arp table after server is accessing an internet resource) Checking my other server (which uses macvlan for now) both br0 and shim-br0 metric is set to 1. I can't change settings on this server since it runs the house now but I assume even with macvlan it should have different metric for br0. For now I did not succeed to reproduce the incomplete arp, before this change it happen within few minutes. I still have the problematic config file, I can try to switch back to it and find the problematic setting if it can help others. I also wonder if it worth switching to macvlan and check if it makes any changes there now. Note: My system doesn't have a network.cfg file now, since I deleted it and did not create any changes from the GUI.

Disabling host access to custom networks does solve the issue but create another issue which I haven't found a solution yet (I have 30 dockers on a custom network and 2 on br0). No I did not modify it, this is interesting since I have 3 servers and all of them are missing it. What is the meaning of this parameter? The 2nd interface was used to make a direct connection between 2 unraid servers. My setup has two servers which act as Active/Passive so if one falls I can switch to the other one. Due to the network issues I physically disconnected the link between them and let the passive server take control since it doesn't suffer from the macvlan issue. I will try to disable bonding. That was my first guess when starting to debug this issue, to isolate it I have uninstalled the plugin, tested that there is no effect and installed it again only changing the cpu governor to powersave without any other changes. Looking at the config file everything else there is set to "default"

Testing with 6.12.3-rc3: Reboot the server for a clean start Check arp table: Wait few minutes, ping google and right after arp is incomplete: Diagnostics attached tower-diagnostics-20230713-2242.zip

Array is stopping correctly with this release and I did not detect any problem, I have also enabled IPv6 just to test it (although I don't enable IPv6 on my servers by default) and webgui loads correctly. Two issues (which are not mentioned to be fixed) are still there: So currently at least for me Docker is not useable yet.

Update: Just for testing I have stopped the array to change docker network type to macvlan, stopping the array (which also stops docker services) is enough to get back network access without reboot. with macvlan the kernel errors are back: Jun 25 14:59:06 Tower kernel: ------------[ cut here ]------------ Jun 25 14:59:06 Tower kernel: WARNING: CPU: 15 PID: 0 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jun 25 14:59:06 Tower kernel: Modules linked in: vhost_net tun vhost tap kvm_amd ccp kvm macvlan md_mod xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_iotlb xt_nat xt_tcpudp veth ipvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ipmi_devintf nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls igb wmi_bmof amd64_edac edac_mce_amd edac_core ast drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ipmi_ssif nvme sha512_ssse3 backlight aesni_intel crypto_simd cryptd rapl agpgart k10temp i2c_piix4 nvme_core i2c_algo_bit syscopyarea joydev i2c_core input_leds ahci Jun 25 14:59:06 Tower kernel: sysfillrect sysimgblt led_class fb_sys_fops libahci acpi_ipmi wmi ipmi_si button acpi_cpufreq unix [last unloaded: md_mod] Jun 25 14:59:06 Tower kernel: CPU: 15 PID: 0 Comm: swapper/15 Tainted: P O 6.1.34-Unraid #1 Jun 25 14:59:06 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470D4U, BIOS P4.20 04/14/2021 Jun 25 14:59:06 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jun 25 14:59:06 Tower kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Jun 25 14:59:06 Tower kernel: RSP: 0018:ffffc900004ec838 EFLAGS: 00010202 Jun 25 14:59:06 Tower kernel: RAX: 0000000000000001 RBX: ffff888151b68400 RCX: 1fd18afb63311d0b Jun 25 14:59:06 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff888151b68400 Jun 25 14:59:06 Tower kernel: RBP: 0000000000000001 R08: e8344bd8ece47fd3 R09: 3d43667ad226f28c Jun 25 14:59:06 Tower kernel: R10: 00afe721eab120e0 R11: ffffc900004ec800 R12: ffffffff82a11440 Jun 25 14:59:06 Tower kernel: R13: 000000000000b05e R14: ffff88817f02cf00 R15: 0000000000000000 Jun 25 14:59:06 Tower kernel: FS: 0000000000000000(0000) GS:ffff889fbebc0000(0000) knlGS:0000000000000000 Jun 25 14:59:06 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 25 14:59:06 Tower kernel: CR2: 0000000000537d30 CR3: 0000000151966000 CR4: 0000000000350ee0 Jun 25 14:59:06 Tower kernel: Call Trace: Jun 25 14:59:06 Tower kernel: <IRQ> Jun 25 14:59:06 Tower kernel: ? __warn+0xab/0x122 Jun 25 14:59:06 Tower kernel: ? report_bug+0x109/0x17e Jun 25 14:59:06 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jun 25 14:59:06 Tower kernel: ? handle_bug+0x41/0x6f Jun 25 14:59:06 Tower kernel: ? exc_invalid_op+0x13/0x60 Jun 25 14:59:06 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Jun 25 14:59:06 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jun 25 14:59:06 Tower kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Jun 25 14:59:06 Tower kernel: ? nf_nat_inet_fn+0xc0/0x1a8 [nf_nat] Jun 25 14:59:06 Tower kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Jun 25 14:59:06 Tower kernel: nf_hook_slow+0x3d/0x96 Jun 25 14:59:06 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jun 25 14:59:06 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Jun 25 14:59:06 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jun 25 14:59:06 Tower kernel: ip_sabotage_in+0x52/0x60 [br_netfilter] Jun 25 14:59:06 Tower kernel: nf_hook_slow+0x3d/0x96 Jun 25 14:59:06 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Jun 25 14:59:06 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 Jun 25 14:59:06 Tower kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Jun 25 14:59:06 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c Jun 25 14:59:06 Tower kernel: netif_receive_skb+0xbf/0x127 Jun 25 14:59:06 Tower kernel: br_handle_frame_finish+0x438/0x472 [bridge] Jun 25 14:59:06 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 25 14:59:06 Tower kernel: br_nf_hook_thresh+0xe5/0x109 [br_netfilter] Jun 25 14:59:06 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 25 14:59:06 Tower kernel: br_nf_pre_routing_finish+0x2c1/0x2ec [br_netfilter] Jun 25 14:59:06 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 25 14:59:06 Tower kernel: ? NF_HOOK.isra.0+0xe4/0x140 [br_netfilter] Jun 25 14:59:06 Tower kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] Jun 25 14:59:06 Tower kernel: br_nf_pre_routing+0x236/0x24a [br_netfilter] Jun 25 14:59:06 Tower kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] Jun 25 14:59:06 Tower kernel: br_handle_frame+0x27a/0x2e0 [bridge] Jun 25 14:59:06 Tower kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 25 14:59:06 Tower kernel: __netif_receive_skb_core.constprop.0+0x4fd/0x6e9 Jun 25 14:59:06 Tower kernel: __netif_receive_skb_list_core+0x8a/0x11e Jun 25 14:59:06 Tower kernel: netif_receive_skb_list_internal+0x1d2/0x20b Jun 25 14:59:06 Tower kernel: gro_normal_list+0x1d/0x3f Jun 25 14:59:06 Tower kernel: napi_complete_done+0x7b/0x11a Jun 25 14:59:06 Tower kernel: igb_poll+0xd88/0xf8e [igb] Jun 25 14:59:06 Tower kernel: __napi_poll.constprop.0+0x2b/0x124 Jun 25 14:59:06 Tower kernel: net_rx_action+0x159/0x24f Jun 25 14:59:06 Tower kernel: __do_softirq+0x129/0x288 Jun 25 14:59:06 Tower kernel: __irq_exit_rcu+0x5e/0xb8 Jun 25 14:59:06 Tower kernel: common_interrupt+0x9b/0xc1 Jun 25 14:59:06 Tower kernel: </IRQ> Jun 25 14:59:06 Tower kernel: <TASK> Jun 25 14:59:06 Tower kernel: asm_common_interrupt+0x22/0x40 Jun 25 14:59:06 Tower kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202 Jun 25 14:59:06 Tower kernel: Code: 17 39 a0 ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 39 f8 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29 Jun 25 14:59:06 Tower kernel: RSP: 0018:ffffc900001cfe98 EFLAGS: 00000246 Jun 25 14:59:06 Tower kernel: RAX: ffff889fbebc0000 RBX: ffff8881086d4c00 RCX: 0000000000000000 Jun 25 14:59:06 Tower kernel: RDX: 00004f3fbe4d29c7 RSI: ffffffff8209093c RDI: ffffffff82090e45 Jun 25 14:59:06 Tower kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 0000000000000002 Jun 25 14:59:06 Tower kernel: R10: 0000000000000020 R11: 000000000000afc8 R12: 0000000000000002 Jun 25 14:59:06 Tower kernel: R13: ffffffff823235a0 R14: 00004f3fbe4d29c7 R15: 0000000000000000 Jun 25 14:59:06 Tower kernel: ? cpuidle_enter_state+0xf7/0x202 Jun 25 14:59:06 Tower kernel: cpuidle_enter+0x2a/0x38 Jun 25 14:59:06 Tower kernel: do_idle+0x18d/0x1fb Jun 25 14:59:06 Tower kernel: cpu_startup_entry+0x1d/0x1f Jun 25 14:59:06 Tower kernel: start_secondary+0xeb/0xeb Jun 25 14:59:06 Tower kernel: secondary_startup_64_no_verify+0xce/0xdb Jun 25 14:59:06 Tower kernel: </TASK> Jun 25 14:59:06 Tower kernel: ---[ end trace 0000000000000000 ]---

I am having the same issue with 6.12.1, I was using macvlan but changed it to ipvlan since I had kernel errors and recommended to change docker to use macvlan. Server has a static IPv4, IPv6 disabled, after reboot everything work well for a while, than server can't access the network (pings from a console to internal network fails), routing looks valid. Server is accessible from then network. Diagnostics attached tower-diagnostics-20230626-0049.zip

The original developer stopped the development, I tried to mainly keep it working. Fixing the docker order requires more effort than my available time right now. If someone is willing to debug and fix it I would be able to merge the changes and release a new version.

Dashboard folders is removed in the latest plugin release, if you still see folders on the dashboard you are not in the latest version. Yes, the dashboard folders were broken for a long time, I did minor fixes, but it needs bigger rewrite to be displayed correctly. I agree, I think basic folders functionally (not everything in this plugin) should be included by default. I assume soon Unraid 6.12 will be released and a thread for next version feature requests will start so it would be a good place to raise this.

For `autostart` there is a workaround for now: Disable `Nuke uptime column`. To do this edit any folder and under "GLOBAL SETTINGS" disable this feaure.

The original developer stopped the development, I was trying to mainly maintain bug fixes, however I am busy in the next month. If someone wants to fix it feel free to make a PR and I will release a new version.

I can confirm that your suggested change resolves the error, Also tested that the condition is running correctly with this change

No, but it is still on my TODO list 🙂

Thanks for updating back, I use Home Assistant but if you can reach the Phoscon UI the docker is working. I would try getting help in Domoticz forums

This is a support thread for the community app docker template, it doesn't look like you are using the template, the default options in the template has VNC mode already set, please first try it, otherwise try to ask for support in the https://github.com/deconz-community/deconz-docker repo

See my previous answer here, there were multiple users with the same problem which resolved by re-installing the plugin:

I have removed them in 6.11, see https://github.com/Squidly271/docker.folder/pull/3 for details, they were broken, couldn't get them to work correctly, so you may left with lines that stay stuck on the dashboard.... Code for drawing them is still there, if anyone have time to fix it, let me know. I may return to this in the future if I have time

Short answer would be from a flash drive backup (which you should do periodically anyhow) Long answer, there is no simple way to recover it, you can follow the steps here Flash should be FAT so many tools can undelete files from there, I am not sure it worth the effort

I helped debugging the same issue few posts ago, something did not reinstall the plugin correctly, please try the following: Backup your current config, you can find it in the flash drive share: flash\config\plugins\docker.folder\folders.json flash\config\plugins\docker.folder\folders-vm.json Uninstall the plugin, make sure the directory above is empty, and reinstall the plugin. Check if it is working, if it is you can try to restore the backup files above.

It is working on 6.11.2

The forked version is bugfixes needed for 6.11, you can't run it on 6.9.2 and won't have any benefit. CA will automatically install the correct version for your OS.

That is not an error, it is just printed in red 🤷‍♂️ About the UI this happens when switching from older version to a newer version, it should be resolved by clearing the browser cache. If you use Chrome, press F12, right click the reload button and select "Empty Cache and Hard Reload"

The USB port is correct, however you need to keep the deCONZ device with /dev/ttyACM0

This usually happens if there is another app using this port. Can you try to change to a different port and check? what else do you see in the log? I have just tested using host network with port 9080 without issues on my test server.

Try to edit a folder (I would start with the "Share" folder), remove the containers, apply the settings, than edit again and add them. Can you attach your `folders.json` file? you can find it under the flash drive share: flash\config\plugins\docker.folder\folders.vm