did i miss a step?
No -- that's a me problem. 
I dropped the weatherstar4k files into the wrong build folder. I guess you're the first one to try it in production. I'll have a new version pushed shortly...
EDIT: It's built -- re-pull and redeploy and you should be good.
Thanks!
I still follow the directions to vnc into the server after one click?
Yes.
1 Like
Its been so long but how am I able to update Olivetin for Channels?
New bnhf/olivetin:latest (aka bnhf/olivetin:2025.11.23) pushed today with Project One-Click support for ESPN4cc4c, ESPN4ch4c and ESPN4adbt. All three can be run simultaneously.
More details here:
Stop the olivetin stack, go into the Portainer-Stacks Editor, and look for the Update the stack button. Use the Re-pull and redeploy slider after clicking the button.
Hey, just curious if anyone has a good guide to get this going on Unraid.
I know there are at least a couple of people that have OliveTin-for-Channels running on Unraid, but nobody's written the process up.
Here are a couple of things to keep in mind:
-
OliveTin-for-Channels requires Portainer -- so be sure you're comfortable with getting Portainer installed and running.
-
A fully functioning OliveTin installation requires access to CVDR executables and recordings directories. If both are on the Unraid server, and you know their paths -- you should be good.
Other than that, if you understand at least basic concepts about Docker and Docker Compose it's not overly difficult.
Thanks, yeah, I was able to get it running with Portainer on Unraid!
I didn't realize that Portainer was required now that I know that it was pretty easy to get up and running!! 
I followed the above method for updating Olivetin and got this message:
Failed to pull images of the stack: compose pull operation failed: failed to create compose project: failed to load the compose file : decoding failed due to the following error(s): 'services[olivetin].environment' environment variable is declared with a trailing space
I am using Portainer (CE) 2.33.5 LTS. I stopped it only in Portainer. Should I have done something within Docker?
Any thoughts?
Try the Docker Compose here:
I believe the one in post #1 here is outdated. If the newer one works, confirm back here and I'll update it in this thread too...
This is the one that I tried. Should I try to other one? I stopped the olivetin stack on in Portainer not docker.
The post you referenced was regarding updating the olivetin container. The error you're seeing indicates the Docker Compose you're using is out of date.
Stop the stack in Portainer, and replace your current compose with the updated one I linked in my last post. You should also confirm the env vars you're using are up-to-date.
The Olivetin stack is stopped in portainer. When I go to OliveTin via web browser, I get this: Error getting webui settings
TypeError: Load failed
fetch-webui-settings error in OliveTin Documentation
This error message will go away automatically if the problem is solved.
Despite not being able to restart OliveTin with Portainer, it is still showing that it is running in Docker and everything is working as it did prior. You have been beyond helpful, but I'm afraid that I don't have the knowledge to go much further. Between this time and the previous time, you've spent a lot of time on this with me and I am sincerely grateful. Should I just stop while I'm kinda ahead (and it's still working??
So I have Portainer CE installed under Unraid.
I frequently have to manually go into Portainer and update OliveTin because it does not do it automatically like Unraid's dockerman. Does anyone who is possibly running a similar setup know of a way to only update OliveTin, possibly through Watchtower, going through Portainer, and leave all of my other containers alone and let Unraid manage them?
Let me start by saying I'm not a fan of auto-updating anything. I use Watchtower, but run it in WATCHTOWER_RUN_ONCE=true mode. However, I understand that some prefer things the other way around.
So, for your desired use case, Watchtower will also work -- but will update all running containers, which is probably not what you want. To get Watchtower to work in this-container-but-not-that-one mode, I believe you'll need to use labels.
These look like this in a Docker Compose:
labels:
- 'com.centurylinklabs.watchtower.enable=true'
When a label is set to true, and Watchtower is configured to only update whitelisted conatiners, a container with the above label will be updated. You can also switch things around and use a blacklisting approach. It all depends on which fits your setup best.
You'll need to read-up to get the results you're after, but it's not difficult. I believe this documentation still applies, despite the project migrating to another repo:
Thanks, I really appreciate it.
I'll look into that!
If you decide to go with whitelisting, which I would guess is best for your scenario, you'd want OliveTin, Portainer and Watchtower itself, to all carry the true label, as shown above.
I got it working. Thanks so much.
Portainer itself actually updates through Unraid. I just need OliveTin and staticfileserver, I believe with the label on it.
Oh and Watchtower also.