Make sure to download the correct .pat file. I believe it is the Apollo lake version.
Just verify your setup. Also, you might want to read the release notes as some versions don’t let you go back to a previous version.
When you get to the point when you're ready to try the EZ-Start process again, be sure you create the directories you'll need first (Synology Docker doesn't create needed directories during stack spin-up, unfortunately). Those directories are:
/volume1/docker/olivetin
/volume1/docker/olivetin/data
Then, when you get to the point where you generating env vars for the full version of olivetin, change the HOST_DIR value to /volume1/docker.
This is just an advance heads-up for something that has been know to trip-up Synology users in the past. 
@bnhf , as you know, I have CDVR, Portainer, OliveTin for Channels and several Project-One-Click extensions all running on my Synology NAS.
I am finding that the Synology has limited processing power and cannot run more resource intensive containers, like Prismcast. So, I'm looking to start up a new host for containers on a rarely used Windows PC I have in my office.
Is OliveTin EZ-Start the best (easiest) way for me to get a second PC based server/host up and running?
I don't know if I'll migrate everything over right away. But, it may prove to be the best direction for me to head (incrementally). That way, the NAS can do what it is designed for...store media and other files. And the PC can be dedicated to running some, or all of my Channels DVR and related programs.
Yes. Use the EZ-Start process to get Portainer and the full version of OliveTin up-and-running. Make sure you're Docker Desktop is up-to-date, and that you have a WSL2 Linux distro installed (like Debian), with WSL2 distro integration enabled in Docker Desktop settings.
This is where I may get lost... I have absolutely no experience with Linux... I'll give it a try. I've been through the EZ-Start process before and don't expect much trouble there. Thanks!
thanks to all. I was able to update to a DSM 7.2 version and now have container manager version 24.02 running. Will Olivetin and Portainer be happy now?
Should be, but be sure you do this:
As an option, Marius Hosting has a step by step tutorial with pics for installing Portainer on Synology.
Just search in DuckDuckGo.
It’s not as easy as @bnhf but the pictures really helped me.
BTW, you can't use this version of EZ-Start if Portainer is already installed. This version would be required:
Overall, I recommend using this version as it's just EZ'er, start-to-finish.
installed olivetin. Went to buttton to install portainer and got error "client version 1.53 is too new. Maximum supported API version is 1.43". Running container manager on Synology DSM218+ DSM 7.2
1 Like
OK, let me play around with options to deal with this for a bit, and I'll get back to you...
EDIT: I'm going to add a test, to the olivetin container startup process, that will check for older Docker API versions -- and then pin support to that older API. This will take a bit, but I should be able to get something out later today.
Is there any downside to me just manually deploying a portainer container?
@rss7 I've added an API test described above, and it should pin the Docker API version to yours now. I don't have any older versions of Docker lurking about, so you'll be the tester . Let me know how it goes, but I think this should sort things out.
I already built a portainer container manually and just used it to get mlbserver and EplusTV working. Can I stll do the test for you somehow?
Unfortunately not.
I think that I'm part-way there. I have installed Ubuntu and Debian and enabled WSL2 integration in Docker Desktop.
I have also installed the Olivetin EZ-Start version on port:1338. It is working.
I ran the Portainer Volume Creation for SMB Shares action to create channels-dvr and channels-dvr-logs volumes.
I have run the OliveTin Environment Variables Generator/Tester action and saved my results to notepad for my own reference.
In running the Create an OliveTin Stack in Portainer action, I used all default values with the exception of toggling volume_dvr1: true and volume_logs1: true.
My result:
exit status 1
JSON response from http://192.168.1.200:9000/api/stacks/create/standalone/string?endpointId=1:
{
"message": "Invalid request payload",
"details": "Json: invalid character 'U' in string escape code: \"C:\\Users\\jsful\\docker\\olivetin\"..."
}
false
Now I'm stuck and don't understand what I have overlooked.
If you're installing a second CDVR server and a second OliveTin, there's no need to use SMB. I'm assuming you want use the second OliveTin with the second CDVR server, of course. The Generator/Tester should have provided you the correct paths to your log files and data files based on values it got from CDVR.
I was not planning on installing a second CDVR server since my native installation on the Synology is working well. This is likely the source of my problem. I want a second instance of Portainer and Olivetin on a different device than my CDVR server.
My current goal is to move Prismcast to a computer which is more capable of running complex tasks. The Synology is currently running Prismcast. But, it really struggles just to keep a single channel up.
I may eventually migrate other more resource intensive containers to my spare computer. But right now, I just want to get Olivetin running and move Prismcast to the PC.
I think I'm with you now. Your Docker Volumes are not set up correctly then. They shouldn't have the Windows path from another PC, but rather should be using the IP address or hostname of the server, and then the share name -- each in their respective fields in Portainer-Volumes (with CIFS enabled). You'll also need to provide the username and password to access that remote share.
Yeah, that's it. I tried to follow along with your advanced instructions: OliveTin EZ-Start: The Next Generation. Deploy OliveTin-for-Channels from the Command Line without the Need for Portainer to be Installed in Advance! - #16 by bnhf
I included separate ip addresses for the CDVR and Portainer Hosts, But, got fouled up along the way. I'm sure that I have the volumes messed up.
TAG=latest
DOMAIN=
HOST_PORT=1337
CHANNELS_DVR_HOST=192.168.1.100
CHANNELS_DVR_PORT=8089
CHANNELS_CLIENTS=
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_EMAIL_FROM=REDACTED
ALERT_EMAIL_PASS=REDACTED
ALERT_EMAIL_TO=REDACTED
UPDATE_YAMLS=true
UPDATE_SCRIPTS=true
TZ=US/Pacific
HOST_DIR=C:\Users\jsful\docker\olivetin
DVR_SHARE=/volume1/ChannelsDVR
LOGS_SHARE=/var/packages/ChannelsDVR/target/channels-dvr
TUBEARCHIVIST_SHARE=/volume1/ChannelsDVR
DVR2_SHARE=
LOGS2_SHARE=
TUBEARCHIVIST2_SHARE=
DVR3_SHARE=
LOGS3_SHARE=
TUBEARCHIVIST3_SHARE=
HOST_SFS_PORT=8080
FOLDER=/web
PORTAINER_TOKEN=REDACTED
PORTAINER_HOST=192.168.1.200
PORTAINER_PORT=9443
PORTAINER_ENV=1
PERSISTENT_LOGS=false