How can I check when the docker container is updated ?
We really need a way to restart the pi from the console.
I sent some request on /api/text-to-intent but I guess too many, or too fast, it crashed rhasspy. The console was still accessible, but no wakeword, nothing responding.
BUT, actually, reboot the pi, the docker DOES NOT start automatically !
So yes, I can close / don’t need ssh, but I can’t unplug/replug the pi when it is not reachable and have rhasspy running without getting a PC, an ssh console, and run it.
We really need something on this, not production ready just on this aspect alone.
This is special. My docker setup on Raspbian Buster always starts automatically.
With the following commands I have installed everything:
Docker install:
curl -sSL https://get.docker.com | sh
Add User Pi to the Docker user group:
sudo usermod -a -G docker $USER
Restart!!!
Install Rhasspy Image in Docker:
docker run -e -p 12101:12101
–restart unless-stopped
-v “$HOME/.config/rhasspy/profiles:/profiles”
–device /dev/snd:/dev/snd
synesthesiam/rhasspy-server:latest
–user-profiles /profiles
–profiles de
For me the Docker engine also starts automatically on Raspbian Buster and restarts all containers that have –restart unless-stopped . So @KiboOst this looks weird to me, what installation instructions did you follow? This isn’t a Rhasspy problem, it seems to be a problem with your Raspbian installation.
I’ve installed it exactly like you.
Get raspbian buster lite, etcher, ssh file, boot and then installed seed driver picotts then rhasspy docker like you.
Do a sudo reboot in ssh, rhasspy doesn’t start
We really need as easy as possible setup 
What does docker ps show after a reboot?
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
42a21bcbd5a7 synesthesiam/rhasspy-server:latest “/run.sh --user-prof…” 28 hours ago Up 2 hours 0.0.0.0:12101->121 01/tcp charming_maxwell
Seems to be running?
ah sorry, missed to reboot:
Just rebooted, and now it is up without doing anything !
Maybe that was due previous unresponding state, strange !
Will keep an eye on this 
How can we know a new rhasspy docker container is available ? To know when doing an update
Hi,
i installed Rhasspy and Home Assistant with a venv and i took inspiration from https://www.home-assistant.io/docs/autostart/systemd/ to start Rhasspy at boot
Disclaimer : it is not really safe to start it as pi user but i could not find a way to make it work with un unprivileged user :
sudo nano -w /etc/systemd/system/rhasspy@pi.service
and here is my service :
[Unit]
Description=Rhasspy
After=network-online.target
[Service]
Type=simple
ExecStart=/home/pi/rhasspy/run-venv.sh --profile fr
Restart=on-failure
RestartSec=5s
[Install]
WantedBy=multi-user.target
Then to enable it like this :
sudo systemctl enable rhasspy@pi
3 Likes
I saw you use docker run -e
when the doc say
docker run -d
What is the difference ?
Also, to stop it, we should run:
docker stop rhasspy-server
but the running instance always have a names like 54dsts13ts, how can we start the container always with same human name (rhasspy-server) ?
I use -d indeed.
Regarding the name simply add --name rhasspy-server to the docker run command.
1 Like
Is there a way to pull the last commit of rhasspy and rhasspy-nlu into the container ? Or does I can only wait for a new version of the docker container ?
You can do what you want within the container (git clone, mv files, etc.)
Enter the container bash with:
docker run -it rhasspy-server bash
Then do whatever you want with the container files.
Once you exited the container bash, you can save the changes with:
docker commit rhasspy-server
Please note that pulling a new image version will overwrite your changes.
Nice !! Will try that, many thanks again
Ok, back to venv, with new service doc, but no way.
Have follow the doc, created service, but can’t train at all
[ERROR:526407] main: [Errno 13] Permission denied: ‘/home/pi/.config/rhasspy/profiles/fr/sentences.ini’
Also have lot of “network connection error” and
wsproto.utilities.LocalProtocolError: Connection cannot be closed in state ConnectionState.CLOSED
And finally after updating from git:
Will shutdown everything and try a new fresh install I guess, but not before a few days.
Still have not been able to see what rhasspy can offer after so much trouble with venv and docker. Promising for sure, but getting it running fine is another story 
Wow, now closing the ssh session with rhasspy running as service, and boom, no more rhasspy.
Unplugged, replugged (set all from the doc to get running at startup), still nothing.
Throwing all this 
I’m using hassio and installed rhasspy as addon
Now issues so far… I can start/stop it in a single click or just by automation
The only thing I haven’t done yet is to monitor current state. But it’s not a problem I think
For me docker also autostart on raspberry pi boot but only when pi connected with laptop through ethernet, if pi start only with usb power without any lan interface rhasspy docker seems not working or not starting on boot …
can anyone guide in this …
Thanks in advance…