KeithRBrown

Hi folks. I've been using FolderView2 for some time now, but decided to update to FolderView Plus. Everything is working great, apart from it's not recognising that a container has an update available. As you can see in the screenshot, I have a folder for Nextcloud, and the MariaDB container has an update available, but the folder still shows "up-to-date". The other screenshot is the settings page for the folder, where I noticed the "DOCKER SIGNALS" section shows "Updates: 0/2". Not sure if this is related, but it's as far as my diagnosis has led me. I've tried clearing my browser cache (I'm using Chrome), and I've even cleared all the FolderView Plus configuration that I imported, and started from scratch, but I still get the same issue. Am I missing something in the configuration?

Unfortunately, I don't have another VM which I can copy. Anyone else managed to fix this?

I'm getting the following error in docker container log Any ideas?

Thanks @binhex - Also working for me after update (and back on my custom docker network). Thank you!

Like others, I'm getting the same issue, but after investigating it a bit (I'm no expert btw), I realised that changing the docker network type from custom (which is what I've using) to bridge resolved the issue. The issue appears to be with resolving DNS using the custom docker network DNS server 127.0.0.11. Not sure if this will help anyone, or assist in fixing the root cause, but I thought it wouldn't hurt to post.

Right, I've tried everything I can find on the forum, including a completely default network / network-rules config, and I cannot get 6.10.2 to work with my configuration. Basically, my main network interface is on a Mellanox 10Gb card, and 6.10.2 completely refuses to recognise this as eth0 (even if I set it as eth0 in the config, when it boots it renames it). In 6.10.1, everything works absolutely fine, so I now find myself in the position not being able to upgrade to 6.10.2. Hopefully someone can shed some light on this. Thanks

What kind of network config issue would only come into effect after upgrading to 6.10.2? Everything is working fine at 6.10.1. Would the 'intel_iommu=off' workaround be worth trying?

I have had the same issue as the original post after upgrading to 6.10.2. After regressing back 6.10.1, everything is working again. Diagnostics attached. clifford-diagnostics-20220528-1336.zip NOTE: I didn't try disabling VT-d, as my BIOS doesn't have that option. I did try the empty tg3.conf file, and that didn't work for me.