ovos-core VS watchtower

Check out OVOS.

I used to work for Mycroft, so I'm hoping to eventually create an image that's compatible with Home Assistant pipelines.

For now, though, you may want to check out OVOS: https://openvoiceos.com/

Blast you're so right! I already ordered an M92, but when LLaMA takes off for voice assistants and I max out my RAM I shall have a think about that HP G2!! With one of those maybe I could have enough RAM to run openbsd and have several VMs running on it! Thank you :D

The upper NUC is running a manual install of ovos-core with sound output through the 22" touchscreen monitor and a kinect V1 as a microphone.

Good news, everyone! As those of you who are following OpenVoiceOS GoFundMe campaign may already have spotted, we've surpassed our most recent fundraising target, and set a new one. Our current stretch goal is a doozy. We're looking to give the Assistant a personality! More specifically, a configurable personality, to make your Assistant that much more... yours.

However it did not work for me out-of-the-box. I had to create some custom Dockerfiles to make adjustments to some of the images before all of them would start up correctly. i got around the Rapidfuzz issue you ran I to using the fix described here: https://github.com/OpenVoiceOS/ovos-core/issues/267

OVOS : There's a Dockerfile in the core repo that you should be able to use to make a Docker image for headless OVOS-Mycroft. You'd probably still have to set up the personal backend for it - not sure as I haven't set it up yet. This is likely the voice assistant replacement route that I'm going with, when there is time to do it.

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!