primeval_god

It is not possible to upgrade the docker engine as a stand alone component. You will have to wait for the unraid os to catch up to the version you are looking for. In the interim you could spin up a VM or an LXC container and run a nested docker engine if you wanted to play around with those new features.

Yes I believe that the unRAID explicitly stops all containers before stopping the docker daemon.

Is it all containers or just specific ones?
What kind of network are the containers attached to (host, bridge, macvlan, ipvlan, other)?
What does the webui field in the container template look like?

Possibly, if it ends up being problem with the Folderview2 plugin you would need to ask in that plugins support forum.

I am not sure you need to modify the image at all. I think you could just change the docker run command. Change the CMD portion of the docker run command to something like sleep infinity
and change the -it flag to -d to run the container in detached mode.

What you are likely doing wrong with docker is referencing the video file path on the host not in the container. Since you are using docker exec I assume you have the container h264_nvenc already running on your system. You need to first make sure that it has the folder "/mnt/user/Video - Files/" mounted into the container. You need to determine what folder in the container it is mounted to, then your conversion command needs to reference the path within the container. Personally i like to mount my video conversion folder to something simple like /mnt/convert in the container.
 
p.s. Also just as a general rule (not for unraid for everywhere all the time), you should not have spaces in directory names.

Probably yes. What kind of network is br0.10
Based on the above it looks like you are trying to make Spoolman available with a dedicated IP address rather than via the host IP. If that is the intent then you can just remove the port mapping from the template and Spoolman should be accessible via port 8000 at its IP address. The port mapping function maps a container port to a port on the host system for which there can only ever be one mapping per external port. Giving a container its own IP address exposes the container directly to the network making all its ports accessible without need for mapping. 

Potentially yes. Typically each cable (or connector) on a PSU represents a separate power "rail". While the power supply may total 850w, each rail has a lower limit. Often times the label on the side of the supply will have information of the distribution of power between the rails. I typically spread my drives out between as many drive cables as my psu has available.

Yes assuming that v7 is released during your 1 year of updates period (which at this point seems extremely likely). See the FAQ section on this page https://unraid.net/pricing for specifics of how the update period works.

It looks like you are trying to access compose files from the compose plugin in some other application. This is not recommended. You really should not mess with the files in the compose plugins project directory.
 
If you must access compose files from something else the compose plugin has an option, when creating stacks, to choose a directory in which to store the compose file, that allows you to place it on the array or in a pool rather than on the boot drive. This also separates the compose file itself from the files compose manager uses to manage the stack.

SMR disks perform poorly in RAID arrays (including the unRAID array). If i remember correctly Drive Bender is not actually RAID, it used disk pooling and some sort of file level redundancy.

I dont think docker on unRAID uses the authz plugin

This can be a point of confusion for many new users. The term Array will hopefully soon be a legacy term (the term not the functionality).  The term "Array" refers to the currently singular, currently required pool that uses the proprietary unRAID redundancy scheme. Here is a more in depth post I made to try to explain the concept a while back 
 

It is but it is not recommended. Containers run through the console will not be particularly controllable via the webui.
 
There is a plugin which installs compose and allows for managing basic compose stacks via the webui. Like dockerman however its designed to support compose stacks run through its ui interface not via the console or other methods. Compose stacks launched via means other then the composeman interface will not integrate with the interface. 
 
If your goal is just learning docker or learning to manage docker systems in general i would not recommend unRAID as the way to do it. unRAID is not a general docker host. unRAID focuses on docker containers as convenient way to have "apps" rather than being a general host for the myriad of other ways containerization can be used (microservices, clusters, C/I setups, etc). Many of the best practices of docker on unRAID are not the more general docker way of doing  things (bind mounts preferred over container volumes for instance or running everything as root). If learning about docker is your goal i recommend using a VM or LXC container with a more general linux OS to host your container playground. Leave unRAID the unRAID docker host for running your important NAS services (media servers, backup servers, sync etc.).

This. Multi-user management is simply not a feature of unRAID (either officially or through community plugins). Generally i try and dissuade people from considering unRAID for business purposes as its security, update cadence, support options, and overall design goals are focused on home use cases. More specifically for your case i would not be comfortable basing business infrastructure on some custom workaround for an unsupported feature (multi user). 
 
If the above doesnt convince you my suggestion would be not to run your multi-user VM/containers directly on unRAID. Nest them within a VM with an OS that provides the multiuser control you need.  

unRAID requires a 64bit processor. https://docs.unraid.net/unraid-os/getting-started/

No, the Dockerman system has its own method of storing the current and latest available version of docker images. Compose.Manager does not integrate with Dockerman in this respect (in fact it does no update tracking of its own it just provides a button with runs a stack update command). 
 
No, at the moment there is no good way to remove the "Update Available" link.
 
The pings are from the Fix Common Problems plugin correct? Best to just disable the update check in FCP.

It is an unRAID concept. There is little more to it than placing all of the docker engine's internal stuff into a disk image to make it easier to manage in a system without the normal persistent install locations.

The guide is not directly applicable to unRAID. unRAID (thankfully) does not use systemd, and changes to its system files are not persistent across reboots. You would have to write a script to make the changes required to put docker in a cgroup (whatever those are) and run it on start before docker starts.

Not a bug but rather misleading documentation. Isolation is for VMs. Pinning if for dockers. 

There is not. unRAID users are not users in the linux sense. unRAID only really supports user access control at the share level through SMB.

I dont know for sure but i would suspect it is the file integrity plugin. The "Changed" time reported by stat is the last time that file metadata was changed (most docs list permissions as an example of metadata). The file integrity plugin stores its hash value in the extended attributes. What i dont know is if extended attributes are considred metadata in this instance, but i would suspect so.