Post the docker run command (See first link in Docker FAQ). An orphaned image only happens when an error occurs on the docker run. They can be safely deleted at any time
It all works. I think there's something more going on. Unfortunately, the only real clue in your syslog is that the monitor keeps puking and exiting.
If you can't grab diagnostics, then reboot, and toss FCP into troubleshooting mode.
Can you save the attached file onto your flash drive, then
cp /boot/backup.php /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php
/usr/local/emhttp/plugins/ca.backup2/scripts/backup.php > /boot/backupdiag.log
After you get back a command prompt, post backupdiag.log on the flash drive here.
backup.php
The only thing is that (Can't remember, and not going to test) is that any files already queued may go into the previously mapped folders (if you changed the mapping on sab / deluge)
Your path mappings don't match between the containers
Some of the containers are using /data for /mnt/user/downloads, and others are using /downloads. You've got to keep it consistent between all of them.
Software cannot overcome the hardware limitations. The CPU / chipset / BIOS has decided to group those things together. If none of the ACS override settings will split them apart, then there is nothing you can do short of passing through a PCIe card & audio