Sorry for resurrecting old thread, but I find it very interesting and actual, it can help.
I see you are strongly recommending using command line. I will try to go fully GUI way instead, let’s see if it will work 
Because my Synology NAS runs very important services for me, and I’m not as comfortable with command line, I don’t want to mess something up. SSH / command line access is and will always stay off here 
Prerequisites:
- have folders ready for data storage
/docker/storj11/data- empty, and with signed Identitydocker/storj11/Identity - have Synology Container Manager v. 24
- have port 28967 forwarded to the Synology IP address
In Container Manager go to Registry tab and type storj to search field:
Click storagenode and Download
After a few minutes, it will ask for Tag, leave there Latest and proceed with Download. Then the image pops up in Image tab:
Select the storagenode row (not the Name) and click Run above
Give it a name, DO NOT Enable auto-restart at this moment:
On Advanced Settings page fill following:
- Listening ports:
28967 TCP+UDP,14002 TCP - Map folders:
/docker/storj11/Identityto/app/identity,/docker/storj11/datato/app/config - Environment variables - as usually, except:
SETUP = true(will need to change it back to False after first run completed) - Network - change to
host
Summary will be as follows:
Click Done, now the node will start, and stop immediately as setup is completed (Synology will report Container storjlabs-storagenode-1 stopped unexpectedly…, that’s fine)
Since Synology does not allow changing any Variables, they recommend to do it by duplicating the container.
Click on the container name (not on the Image name)
Click Duplicate
Change only following settings
- turn on
Enable auto-restart - in my case it does not remember Port Settings so I need to set them up again (refer to above)
- change SETUP to
false
—That’s all folks —
Now you can delete the first container - that is not running
Now you will see the folders created and filled:
Container Details (It is not showing Network utilization, not sure why)
Starting to consume RAM 
Log:
this is not good though, the logs will not load any longer once the number is higher, it keeps Loading forever, we will need to redirect logs to a file (TBD)
