Installing BalenaSound with Hoobs

Product support balenaOS
, ,
1

Hi Guys,

First of all I don’t have a lot of experience with Docker, so perhaps my issue is fairly simple. Yet, I did not find anyone online with a solution.

MAIN GOAL
I want to run on my raspberry pi BalenaSound(for now 1 device), and Hoobs(Homebridge Out Of the Box). I tried with homebridge as well but without success.

I can install correctly and working the BalenaSound, but it seams Hoobs is stuck on start saying : “Installing service 'hoobs sha256XXXXXX”

The main questions are : Is my docker-compose ok? will this be enought to download the image and install it?
Do I need a start.sh file ? if so how do i know it is running?

version: ‘2’

volumes:
spotifycache:
hoobscache:

services:

audio:
build: ./core/audio
privileged: true
labels:
io.balena.features.dbus: 1
ports:
- 4317:4317

sound-supervisor:
build: ./core/sound-supervisor
network_mode: host
ports:
- 3000:3000
labels:
io.balena.features.supervisor-api: 1

multiroom-server:
build: ./core/multiroom/server
restart: on-failure
ports:
- 1704:1704
- 1705:1705
- 1780:1780

multiroom-client:
build: ./core/multiroom/client
restart: on-failure

bluetooth:
build: ./plugins/bluetooth
restart: on-failure
network_mode: host
cap_add:
- NET_ADMIN
labels:
io.balena.features.dbus: 1

airplay:
build: ./plugins/airplay
restart: on-failure
network_mode: host
privileged: true
labels:
io.balena.features.dbus: 1

spotify:
build: ./plugins/spotify
restart: on-failure
privileged: true
network_mode: host
volumes:
- spotifycache:/var/cache/raspotify

upnp:
build: ./plugins/upnp
restart: on-failure
network_mode: host
ports:
- 49494:49494

hoobs:
image: hoobs/hoobs
container_name: hoobs
environment:
- PUID=1001
- PGID=1001
- TZ=Europe/Amsterdam
volumes:
- hoobscache:/opt/appdata/hoobs:/hoobs
ports:
- 8080:8080
- 8181:8181
- 51826:51826
restart: always

Thanks guys.

5

Hi there, are you following this tutorial? https://www.balena.io/blog/two-projects-one-device-turn-your-raspberry-pi-into-a-multitool

I don’t see anything specifically wrong with you compose file. Though it might be good to check if HOOBS runs on it’s own before merging the compose files.

Also these docs explain a bit more on how to merge two projects: https://www.balena.io/docs/learn/develop/multicontainer/#docker-composeyml-file

7

Hi StefJKors,

I left only the hoobs part of the docker-compose and I get the same error: installing service 'hoobs sha256:XXXX…"

Is there a way to debbug why the container is not installing the image or get any other information about the issue?

At this moment I only have HOOBS on my docker-compose and I get the same error.

EDIT: I Followed that tutorial.

8

Hey there,

Am I right you are using a Pi4? If so:

Can you update your docker-compose to point to the Pi4 specific docker image for hoobs and try again? It should look like this (also not the change to the volumes line):

    hoobs:
        image: hoobs/hoobs@sha256:85f90f0e6eb6ae2284922bc58db55c1b2deb53e92b4b76c0c350afbe2fe4109f
        environment:
          - PUID=1001
          - PGID=1001
          - TZ=Europe/Amsterdam
        volumes:
          - hoobscache:/opt/appdata/hoobs
        ports:
          - 8080:8080
          - 8181:8181
          - 51826:51826
        restart: always

Phil

15

Thanks phill, I have tried that but i get the same error.
Thanks

16

Hey again - did you use my snippet of docker-compose ? I have that exact thing running on a Pi4 now, with no problems.

18

Hi phil,

Thanks for the snippet, I tried again an it is running hoobs. Although balena is saying it is running on port 80 but i cant seem to find it. Where is it running? R

Regards

19

Have you tried checking for Hoobs running on port 8080?

20

Hi Markcorbinuk,

I tried but is not there too

21

Please could you post a copy of your updated docker compose file - thanks.

22

version: ‘2’

volumes:
hoobscache:

services:
hoobs:
image: hoobs/hoobs@sha256:85f90f0e6eb6ae2284922bc58db55c1b2deb53e92b4b76c0c350afbe2fe4109f
environment:
- PUID=1001
- PGID=1001
- TZ=Europe/Amsterdam
volumes:
- hoobscache:/opt/appdata/hoobs
ports:
- 8080:8080
- 8181:8181
- 51826:51826
restart: always

23

I’ve run some tests with your docker compose file…
Hoobs is listening on internal container port 80, so you need to change the ports line to - nnnn:80 where nnnn is an external port that’s not being used by another container, e.g. - 80:80 or - 8080:80 etc.

Regards

Mark

25

Thank you so much! Now it is working on port 80 with nnn= 80

Regards