tjb_altf4

Nextcloud (docker) might be a nice way to handle this, particularly for the less technology literate users you may want to share content with.

There is no GUI interface for creating or deleting docker networks (I'm assuming this is what you are referring to).
Instead you need to go into the CLI and type: docker network rm <my-network>
Where <my-network> is the name of your network to be removed, this can also be stacked if you like e.g. docker network rm <my-network1> <my-network2> <my-network3>
 
If you don't know what networks you have, type docker network ls
The Unraid default docker networks are br0 (and br1, brx etc for each interface), bridge, host, none and wg0
 
Note that any containers still configured to use that network will fail to start, but you can adjust this in the docker settings.
If a containers is still running and using one of these networks the command will likely fail to remove it.
 
Example:
root@fortytwo:~# docker network ls NETWORK ID NAME DRIVER SCOPE f65acde003bd br0 ipvlan local 8ba0d062c51e br1 ipvlan local b410faa93e33 bridge bridge local f14e96c2b3e7 go-spacemesh_spacemesh bridge local 5974bf6e7616 host host local 6ef32c3f7c35 none null local d51a9a1ed7b1 pihole bridge local 6c61ba876986 proxynet bridge local 1fd749e6cfc9 wg0 bridge local root@fortytwo:~# docker network rm go-spacemesh_spacemesh go-spacemesh_spacemesh root@fortytwo:~# docker network ls NETWORK ID NAME DRIVER SCOPE f65acde003bd br0 ipvlan local 8ba0d062c51e br1 ipvlan local b410faa93e33 bridge bridge local 5974bf6e7616 host host local 6ef32c3f7c35 none null local d51a9a1ed7b1 pihole bridge local 6c61ba876986 proxynet bridge local 1fd749e6cfc9 wg0 bridge local root@fortytwo:~#  

Macvlan docker network type is the likely cause of your kernel panics, this is a known issue and such a common problem in recent releases that it is no longer a default setting.
The fix in this case is to change docker network type from macvlan to ipvlan, which involves stopping the docker service:
go to SETTINGS > DOCKER with advanced view toggled (top right), set Enable Docker: No, then set Docker custom network type: ipvlan Once complete:
set Enable Docker: Yes to restart docker service. Report back with fresh diagnostics if kernel panics continue.

Once you have created a pool with at least 4 disks (btrfs), you can convert to raid10 using balance option under that pool's disk settings (click on first disk in pool from Unraid GUI > MAIN).

User Scripts plugin is the easiest way to work with scripting + cron in unraid, it also adds addition events for start/stop of array.
 

The docker folder plugin works with VMs also, which can achieve this effect.
 

Pretty sure vfio binding happens too late to work for the primary display device.
Passing a correct vBIOS should allow the card to be passed to the VM successfully in this scenario.

A3.  Install nerdpack plugin, which allows you to install packages through the GUI, with User Scripts plugin being a nice frontend for running scripts on a schedule.

 
Alternatively you could look at running the scripts through a python based docker.
VM is also possible, normally you would just create a vdisk for it to run on, but passing a whole disk is also possible.

Couple of things to try:
Make sure secure boot is disabled in bios If you need to enable UEFI boot, rename the EFI- directory to EFI

OK after finding a similar report by another user, I decided to reboot as he did and the warning went away as it did for him... Started the array and all is well... thank fk.
 
This is the second time Unraid's BTRFS pool state management has tripped me up, it would be great to see the BTRFS implementation in Unraid get a bit more love before we dive in the deep end with ZFS.