ehrw

If you can add it to the release notes that's visible in unraid that might help. That's at least the first place I check after something has received an update and it doesn't work as expected.

I figured it out. It was related to the docker compose plugin. https://github.com/mstrhakr/compose_plugin Personally I didn't set it up yet. Was considering moving immich over and redoing all of that. Postponed it and forgot about it. It adds a new section at the bottom of the page for docker compose. Probably something interfering there. It worked fine up until this latest update though. Hope this helps someone else too :)

Cleared the cache, tried incognito, reinstalled the plugin and imported my config. Still doesn't work after the latest update. No folders are visible under the docker tab. Still see them under the plugin settings. Any tips?

Wondering the same thing. Currently have speed issues and my router sometimes drops the connection maxing out the port speed via VPN. Their support recommends to set my whole network to MTU 1420 which I ofc doesn't want. Less knowledge about this than the OP. What different ways could you set a custom MTU to a docker container? Is it possible to do it without without running it as privileged?

I suspect this could be related to the problem I had. I have a 10gbit PCI-E NIC that I've changed to ETH0 in the Network settings. After this update this menu is suddenly gone and I can't set the 10gbit NIC to ETH0. My temporary fix was to bond ETH1 with ET0. To change the Network Settings, temporarily stop the VM and Docker service. I'm by no means an expert and know if there's a better solution. It worked for me at least

Same, looks to have stopped working with yesterday mornings docker update. At least for me. Tried a bunch of things without success.

If someone still has issues getting this to work I was able to solve it by using bits and pieces of this thread. 1. Make sure both dockers are in the same mode. Either as Host (remember to change port from port 80) or as custom br0. This is the most common reason they can't communicate 2.There's a newer version of the docker in a different repo. See this post 3. This is how you flash the firmware. During the flashing process. Double check the latest version that's displayed. Also look for ConBeeII in the file name. My first time I took the wrong file and it failed Happy Zigbeeing