OliveTin EZ-Start: A New Way to Deploy OliveTin-for-Channels Using Just Two Environment Variables to Get Started!

[bnhf]

@ZWells

HOST_DIR=/data

This is a problem too -- on Synology. On that specific NAS, Docker can't create directories -- they need to already exist. I believe /volume1/docker/olivetin is a good option. Make sure (using File Station) those directories exist first. Create them if needed. This is required for all containers, and is a Synology-Docker issue.

EDIT: Also, create /volume1/docker/olivetin/data for static-file-server...

[ZWells]

Understood. This update did the trick.
I tried the Tubi project. This installed. The MLB one click did not. The Roku Bridge Container is generated but I'll have to address this in the Custom channels in CDVR I think.

[bnhf]

@ZWells

I tried the Tubi project. This installed.

Glad to hear it.

@ZWells

The MLB one click did not.

Error messages?

The docker composes used for anything in Project One-Click are shown here, or can be displayed in One-Click:

A docker-compose for every Channels-related extension -- suitable for Portainer-Stacks!

I've just updated my docker-compose examples, in OliveTin-for-Channels, for the many excellent container projects that are suitable for use with Channels -- via the WebUI for Docker -- Portainer. I thought I'd post them here as well, for anyone not using OliveTin yet. The idea with the way these yamls are structured, is that you shouldn't need to do ANY editing of the yaml itself, all installation specific values should be set via the environment variables in that section of Port…

This will help you figure out what directory to create before trying to spin-up a container. Only certain directories are writable on Synology. Using /volume1/docker as a parent (as opposed to /data) is a reasonably safe bet.

@ZWells

The Roku Bridge Container is generated but I'll have to address this in the Custom channels in CDVR I think.

The Roku Bridge requires configuration before you can create your CDVR source. One-Click always does this if possible, but some projects need configuration before proceeding.

[ZWells]

FOR MLB error:

 JSON response from http://192.168.1.20:9000/api/stacks/create/standalone/string?endpointId=2:
{"message":"failed to deploy a stack: time=\"2026-01-19T20:30:09Z\" level=warning msg=\"/data/compose/24/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion\"\n Network mlbserver_default Creating\n Network mlbserver_default Created\n Container mlbserver Creating\n Container mlbserver Created\n Container mlbserver Starting\nError response from daemon: Bind mount failed: '/data/mlbserver' does not exists\n","details":"Failed to deploy a stack: time=\"2026-01-19T20:30:09Z\" level=warning msg=\"/data/compose/24/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion\"\n Network mlbserver_default Creating\n Network mlbserver_default Created\n Container mlbserver Creating\n Container mlbserver Created\n Container mlbserver Starting\nError response from daemon: Bind mount failed: '/data/mlbserver' does not exists\n"}
false

[bnhf]

@ZWells

Error response from daemon: Bind mount failed: '/data/mlbserver' does not exist

As discussed, you can't use /data as a parent on Synology. You should specify /volume1/docker as a parent, but be sure to create /volume1/docker/mlbserver using File Station first.

[ZWells]

Ok, I got MLB to work. Samsung is working. The Weather4000 is up next but is asking for a cc4c Host. I don't know what this is but I'll have to research. Thanks so much for your help.

[chDVRuser]

There are some projects that probably won't run well, if at all, on a low powered Synology NAS.
Those are meant for beefier machines.
I would recommend looking at the threads for the projects before you try installing them.