I use rhasspy master/satellite with Docker. And know nothing about docker compose !
As my rhasspy setup is now in production ( ) and just receive a new Pi4 to test future versions and try different thing, I would have a look at it.
I get the abstract, creating a yml file with all settings inside, instead of running docker with plenty or params for devices, volumes, ports etc.
installation
Is there a better install cmd line to get latest stable compose version on a Pi/Buster ? I see different one with version into …
I see every settings goes into docker-compose.yml.
So, I guess we can’t rename this file ? And where goes this file ? Do you let it in /home/pi ?
Or do you create a /home/pi/rhasspy and run rhasspy/docker-compose up ?
This is really not clear
using
If I’m correct, from what I have read here and there:
docker-compose up -> start container according to yml settings, download images if needed. docker-compose up -d -> start container in background ?? docker-compose down -> stop and rm the container (but let volumes ??) docker-compose down --volumes -> stop and remove everything ?
So, if a new rhasspy docker image is published, to update I would have to:
docker-compose down -v
docker-compose pull
docker-compose up
right ?
Stuff like differences between start/up and rm/down
Starting from a pi with docker, should I delete all rhasspy images/containers before installing and setting compose ?
What I like about Swarm is the ability to deploy a service as “global” (there will be one instance of this service on each node with affinity, etc). So once you have defined your deployement, adding a new satellite is as simple as setting up docker and joining it to the swarm.
Problem is that it works without the .alsaequal.bin file but can’t get it running with it. being -v option or type bind option.
ERROR: for rhasspy Cannot start service rhasspy:
OCI runtime create failed:
container_linux.go:370:
starting container process caused: process_linux.go:459:
container init caused: rootfs_linux.go:59:
mounting "/home/pi/.alsaequal.bin" to rootfs at "/var/lib/docker/overlay2/4757877b33e95e830c98d500f9704ee2e302d9714ba738bc5e5e4ddb036c2e6c/merged/home/pi/.alsaequal.bin" caused: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Seems a nice and elegant solution to set container parameters one time, indeed.
I guess docker-compose parse yml file, and under the hood it just start a docker run with all parameters ?
What’s the impact of docker compose on cpu / ram ? I guess it’s a few commands interpreter than run docker and close itself ? Nothing running in background (daemon, services) ?
Hi @fastjack,
As I’ve several satellites and a bit lazy (and curious) and also got Portainer alrready installed as an HomeAssistant add-on, would it be possible to use it to manage the updated of my “mini-park/mini-infrastructure”.
If so, have you any recommendation for a tutorials/step by step guide (for noobs )