Squid

The pics you've posted are broken links. And also what OS version are you on?

Just pointed out to me. Working it

Keeping. Doesn't affect anything

The permissions would be incorrect. Use Krusader or File Manager (both available within Apps) to delete or alternatively the command line

So everything works though if you boot in one of the NON GUI modes and you access via another computer? (this is how 99.9% of the times you would manage the system. Fundamentally, GUI mode is there if your daily driver you use is a VM on the Unraid Server itself. Curious if when booting via the non-gui mode after you log in at the prompt and then enter in the command slim if the GUI comes up.

Instead of using your router as your DNS servers, setup DNS #1 and #2 with a dedicated DNS server. Use 208.67.222.222 and 208.67.220.220 (OpenDNS servers)

This all looks like an actual terrible USB flash. (Or possibly a counterfeit one)

Safe to ignore

IDK. What this plugin very slightly changes on 6.12.8 isn't needed on earlier OS versions

Depends upon your point of view. Since 2015, I've never even considered leaving an "empty" path on any docker template and instead of simply deleted the path from the template. With 6.12.8, docker is now enforcing a specification and returning an error if you left an empty path on a template when installing it or updating it. Since there is already a number of users with this issue (self-caused), the plugin is changing how the docker run command gets generated to ignore this problem. There is NO bug with the OS. There is NO bug with docker. The plugin lowers support requests in the forum on what the issue is when all of a sudden they update their containers and they disappear. You don't need the plugin if you have no templates with empty paths and always delete any empty paths on new installations from CA.

This plugin has nothing to do with any other settings etc you may have. I've moved your posts (and itimpi's) to here

no

I'd recommend to install the Docker Patch 6.12.8 from Apps due to docker now treating as an error a common mistake that users may have made (leaving unused paths empty on the template) when installing from Apps. It's not a bug in the OS, but now docker enforcing their specification on the run command

Changed Status to Solved

This plugin does a quick patch to the docker system on 6.12.8 only to prevent any empty host paths or container paths which may be present in an already installed template (or on a new installation) from triggering an error (and creating an orphan image) when updating the application. This is NOT fixing any bug in Unraid at all. Previously, the docker run command (eg: on 6.12.6) would not return an error if there was no container path specified. The docker system in 6.12.8+ does return an error (which is the proper operation). This quick patch simply has the docker system not add in to the docker run command any paths which has either the container or host side of it blank. If you did update an application and then had it orphan due to an empty path, then simply installing this plugin and then going to Apps, Previous Apps and reinstalling will get you back and running without changing the template to how it should be set up

A quick patch plugin will be done shortly. FCP will warn if the plugin isn't there. This isn't fixing any bug but rather changing the behaviour. If there is a bug per se then it's with previous versions of docker

If it’s still there in docker edit it (if not previous apps and actions reinstall) and you have a path sitting in there that doesn’t have an entry next to it. Remove that path

Its from Unassigned Devices. Since you're already up to date on it, reboot and if it happens again post in the UD support thread

OK. What I'll do then is have CA adjust every template on 6.12.8+ to have the paths as required..

6.12.6 fails silently in this circumstance (incorrect behavior) Tested it all and I can get this via the GUI no problems.

Changed Status to Retest

Why would you want to have a container path that isn't mapped to a host path? The docker executables let that slide without an error on 6.12.6 and do indeed return an error on 6.12.8. And the error is correct. Docker silently failed on .6 as it wouldn't create any container path. Now they're calling it an error instead of silently failing. There is a bug here, but it's not that the path is empty. Rather that on editing or creating a container and adding a new path without a host path that you can apply without having it filled out unlike installing a new template with an empty path where it forces you to enter something before you can apply.

Highwater fills the 8tb until it has 2TB free. Then it'll fill the 4TBs in turn until they all have 2TB free then all the drives in turn until they have 1TB free.