Pi zero - docker container restarting in loop

Help
1

Hi,

I’m trying different ways to setup a Pi zero rhasspy satellite.
I did the following:

Then I execute docker run -d -p 12101:12101 --restart unless-stopped -v "$HOME/.config/rhasspy/profiles:/profiles" --device /dev/snd:/dev/snd rhasspy/rhasspy:2.5.0-pre --user-profiles /profiles --profile fr

Unfortunately it restarts in loop
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” 21 seconds ago Up 1 second 0.0.0.0:12101->12101/tcp sharp_bouman
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” 25 seconds ago Restarting (132) 4 seconds ago sharp_bouman
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” 31 seconds ago Restarting (132) 1 second ago sharp_bouman
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” 35 seconds ago Restarting (132) 5 seconds ago sharp_bouman
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” 39 seconds ago Restarting (132) 9 seconds ago sharp_bouman
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” 59 seconds ago Up 2 seconds 0.0.0.0:12101->12101/tcp sharp_bouman
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” About a minute ago Restarting (132) 5 seconds ago sharp_bouman
pi@RPI-ENTREE:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01753aa27695 rhasspy/rhasspy:2.5.0-pre “bin/rhasspy-voltron…” About a minute ago Restarting (132) 9 seconds ago sharp_bouman

Do you experiment similar issue?

fx

2

I don’t have similar issue but I used :

rhasspy/rhasspy:2.5.0-pre-arm32v6

in the command to execute Docker.

Nevertheless, my pi zero satellite (I also use e proxmox VM as a master and a RpiA+ as a second satellite) isn’t reliable. I need to restart rhasppy every hour… No problem with the RpiA+ satellite.

3

I confirm you need to use the image 2.5.0-pre-arm32v6. The one you used is not for Pi zero architecture.

4

Indeed. Thanks @3issa and @maxdel for your help !