balena-io-experimental / balena-sound

Build a single or multi-room streamer for an existing audio device using a Raspberry Pi! Supports Bluetooth, Airplay and Spotify Connect
https://balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/
MIT License
2.45k stars 432 forks source link

sound-supervisor standard_init_linux.go:219: exec user process caused: exec format error #637

Open Galster opened 1 year ago

Galster commented 1 year ago

Hello!

I deployed with balena on my raspi2 and sound-supervisor container wasn't start.

Log:

 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 sound-supervisor  standard_init_linux.go:219: exec user process caused: exec format error
Restarting service 'sound-supervisor sha256:cb53f3535194f84bd5b0e004983544009d8f7c14e01964a9332d8e32d60e2e90'
Service exited 'sound-supervisor sha256:cb53f3535194f84bd5b0e004983544009d8f7c14e01964a9332d8e32d60e2e90'
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80
 audio  Waiting for sound supervisor to start at 172.17.0.1:80

Device health check:

check_service_sound-supervisor 
 Failed User service 'sound-supervisor' is restarting unexpectedly, count: 224

How can I fix it?

ruebe5w commented 1 year ago

Exactly the same problem here with Raspberry 3

ruebe5w commented 1 year ago

I think https://github.com/balena-labs-projects/balena-sound/issues/634#issue-1614187520 is also the same problem

Galster commented 1 year ago

I managed to make it work by changing line #14 in balena-sound/core/sound-supervisor/Dockerfile.template to

FROM balenalib/%%BALENA_ARCH%%-alpine-node:14

adsoccer5 commented 1 year ago

I understand but how does one do this on windows using the terminal host OS (On balenca cloud /dashboard). I having trouble finding these folders?

ghost commented 1 year ago

@adsoccer5 Just figured this out. I don't really have any experience with balena-cloud or GitHub but got there in the end. Hopefully this helps.

alanb128 commented 1 year ago

This should now be fixed...