This was exactly what I needed to move over to the container version - specifically, the container mount points. I configured it from the Synology Docker UI, restored the database, and was backup up and running in no time. If you set it up to use host networking (as you have), you shouldn't need to specify the ports - in fact, the UI prevents you from doing so.
What device are you passing in from /dev/dri?
The host network IP was used to bind to only one of my network adapters. I have four on my old NAS and two on my new NAS.
/dev/dri is needed for hardware transcoding and not available on all Synology models.
In fact, if you used the run command I did and your Synology didn't support that you get an error.
Ok, makes sense. I don't transcode and I don't have a /dev/dri, so I didn't have to pass anything in. Thanks for the example!
I switched from using the Docker UI in DSM and recreated my ChannelsDVR install from command line. It worked great!
Check out: Synology Docker and Transcoding to see what I did
Reading this thread makes me happy Iām running Channels on my PI4 instead of my 218+ 
Why it is very simple at the moment if you chooses to upgrade to DMS7 you have the option to run ChannlesDVR on a docker .. or simply wait until channelsdvr comes out with a compatible DMS 7 SPK ... what is so scary about that ? Sometimes on these threads there is a lot of panic or exaggeration.
The Pi4 is an inexpensive, dedicated unit that is maintained by Channels with auto updates etc. Set and forget. I notice no difference between using it on the Pi4 vs my Synology (I don't do out of home streaming). Not that I'm above updating and tinkering with my NAS, that's kinda fun. I just don't ever have to think about it with the Pi4.
I have it on a NAS and do not think about either even in the event of a drive failure ...
Do RPi's still have the problem of self-destructing after ungraceful shutdowns. E.g.: Power failures?
Fwiw, I run Channels natively on my 918+ and blindly updated to DSM 7.0. No problems so far.
I was going to avoid this release for longer and even had the update blocked in my Pi-Hole. But its a long weekend and there are no fireworks in Baltimore. So it seemed like a good time to play with it. I took the blocks off my Pi-Hole, removed incompatible packages and installed DSM 7. And was quite surprised.
I have numerous shell configurations for nginx, reverse-proxies for various web-sites, scripted auto updates for a multitude of lets-encrypt certificates, and other custom configurations. Often, these get wrecked and need to be setup again after a major DSM update. But that was not the case this time. Everything is working. Including Channels-DVR. I have docker on here, but haven't been running it on the NAS recently. I prefer leaving Docker apps to run on my Pi to keep load down on the Synology. So I'm glad the native Channels install still works.
It should be said that users should never need to reinstall the Channels DVR package. All the actual application updates are done through the app itself, not through package manager.
Anyway, I notice a performance improvement running Channels on my Synology with DSM 7. Just tested watching 3 OTA channels, while recording 5 different OTA channels (these were all high-bitrate OTA HD), while running comskip. + Also recording from 3 HD cameras in Surveillance Station.
Load averages remained lower than I have seen before with this kind of load. IO wait didn't spike like it usually does with 5 recordings and comskip.
This may be unique to my circumstance, as I am running btrfs on RAID 6. And the DSM 7 changelog does specifically list both btrfs and RAID 6 improvements with IO speeds. But I thought I should mention it anyway. I originally said this DSM should be forever avoided. But, after testing for a day, I have changed my mind. This release seems to increase the capability of my DVR.
I am sure that I will still eventually find some custom thing that needs re-configuration after the upgrade. But thats ok, it was worth it in my case due to the disk performance improvements that it added.
Thanks, do you run this after upgrading to DSM 7.0 or before? Not sure I understand what the SPK is for.
If you upgrade from DSM6 to DSM7 then no action is required. The old SPK and installation will keep working.
Thank you.
Help! So I think I might have made a mistake. I performed the Synology upgrade from DSM6 to DSM7 and Channels seemed to be working ok, but I noticed that the version was older than the download file for the new DSM7 version on the Channels website.
So I tried to install the new 1.1.0 version and it failed. It then told me to uninstall the failed install, which I did. Now I have nothing installed and when I try to re-install the new 1.1.0 version it keeps failing saying "Failed to install the package. Downloading Channels DVR 2021.08.12.0054 (linux-x86_64) to /volume1/@appstore/ChannelsDVR/channels-dvr....Channels DRV has been downloaded." On the apps page it shows Channels DVR and says "Error. Please re-install the package because something went wrong."
How do I get it installed, and hopefully with it keeping all of my previous shows and information?
There is no reason to upgrade the SPK.
I think you probably need to delete it completely and reinstall at this point.
Afterwards you can do a backup restore as described here: Channels Support - How do I move Channels DVR Server to a new computer?
See also:
How do I do that? I've tried to uninstall it and reinstall it with the same error? How do I "delete it completely" (without hopefully losing all of my data)?
Any more help would be appreciated as I am now dead in the water 