To get this container to execute in Docker on the latest Synology version (DSM 6.1-15047 Update 1):
The --cap-add=NET_ADMIN parameter isn't supported by the Docker GUI. Without it iptables won't play nice. Instead select 'Execute container using high privilege' under the General settings of the container.
Make sure that mandatory kernel modules are loaded. We got two options (A & B):
A. This won't survive a reboot. SSH as an user in the administrators group to your Synology NAS and run the following commands:
sudo insmod /lib/modules/tun.ko
sudo insmod /lib/modules/iptable_mangle.ko
B. This will recover the loading during the boot. Create a new 'Triggered Task' from the DSM 'Control Panel' -> 'Task Scheduler'. Select user 'root', event 'Boot-up' and check 'Enabled'. As script enter:
Done. //EDIT: User reported he needed to reboot. I can't remember anymore.
Could you please consider adding an option to shutdown the container with a non-zero status if these modules are not loaded (if possible)? Currently the container appears to be running, but Deluge will not be loaded because of these missing modules. It took me some time to figure out why I couldn't reach Deluge.
Also, Synology Docker contains and option (in the GUI) to auto restart the container on unexpected shutdown (non-zero exit status). I think it will append --restart failure to the docker command. If you add this shutdown we will always have enough time to make sure the loading of the required modules is done during the boot-up (using the Task Scheduler).
Thank you so much for the container. The most used 3rd packages source for our Synology NAS systems (SynoCommunity) is currently incompatible with the latest version of the operation system (DSM 6+) and it looks like it will be the case for a long time. So containers like these are essential for us.