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.
Is there a better install cmd line to get latest stable compose version on a Pi/Buster ? I see different one with version into …
sudo curl -L "https://github.com/docker/compose/releases/download/1.28.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose sudo chmod +x /usr/local/bin/docker-compose
I see every settings goes into
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
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
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 ?