eiddor
commented
3 years ago @Philip-A
That's an interesting guide - some of the services in both projects have changed, however, which might explain why it's not working. I may attempt this if I get some time next week, but let me try to answer some questions to see if I can get you a bit further.
I am new to Docker, but in my opinion network_mode: host means that the definition ports: - 80:80 is ignored, because the hosts network interface is used directly without any isolation.
This is correct.
03.06.21 10:02:44 (+0200) sound-supervisor Sound supervisor listening on port 80
This is a brand new change introduced with #453, so yeah you are on the right track by changing the host port since it would definitely conflict with pihole.
The - 80:80 added for that change didn't do anything though because as you've discovered, that container is running in host mode. The problem we're going to have here is that the pihole service is also running in host mode.
You can read this mega-thread where I kind of discover some of these things and it may give you some ideas: https://github.com/klutchell/balena-pihole/issues/66
I end up narrowing it down to a timing issue because I had spanning-tree running on my switch, but there are some pretty neat findings in there if you're the network type at all.
There appear to be a number of other ports that sound-supervisor is actually listening on, however. If I stop all services and compare the listening TCP/UDP ports before starting sound-supervisor this is what I get:
Before starting the sound-supervisor container:
root@balena:~# lsof -iTCP -sTCP:LISTEN
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 53u IPv6 17021 0t0 TCP *:22222 (LISTEN)
dnsmasq 1501 nobody 5u IPv4 20815 0t0 TCP balena:domain (LISTEN)
dnsmasq 1501 nobody 7u IPv4 20817 0t0 TCP balena:domain (LISTEN)
node 3152 root 25u IPv6 29714 0t0 TCP *:48484 (LISTEN)
root@balena:~# lsof -iUDP -P -n | egrep -v '(127|::1)'
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
chronyd 1403 root 5u IPv4 20594 0t0 UDP *:1234
chronyd 1403 root 6u IPv6 20595 0t0 UDP *:1234
NetworkMa 1492 root 23u IPv4 25413 0t0 UDP 10.9.1.62:68->10.9.1.1:67
dnsmasq 1501 nobody 4u IPv4 20814 0t0 UDP 10.114.102.1:53
avahi-dae 26920 avahi 11u IPv4 234858 0t0 UDP *:5353
avahi-dae 26920 avahi 12u IPv6 234859 0t0 UDP *:5353
avahi-dae 26920 avahi 13u IPv4 234860 0t0 UDP *:59008
avahi-dae 26920 avahi 14u IPv6 234861 0t0 UDP *:59252 After starting the sound-supervisor container:
root@balena:~# lsof -iTCP -sTCP:LISTEN
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 53u IPv6 17021 0t0 TCP *:22222 (LISTEN)
dnsmasq 1501 nobody 5u IPv4 20815 0t0 TCP balena:domain (LISTEN)
dnsmasq 1501 nobody 7u IPv4 20817 0t0 TCP balena:domain (LISTEN)
node 3152 root 25u IPv6 29714 0t0 TCP *:48484 (LISTEN)
node 31752 root 20u IPv6 276413 0t0 TCP *:http (LISTEN)
node 31752 root 21u IPv4 276432 0t0 TCP *:8000 (LISTEN)
root@balena:~# lsof -iUDP -P -n | egrep -v '(127|::1)'
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
chronyd 1403 root 5u IPv4 20594 0t0 UDP *:1234
chronyd 1403 root 6u IPv6 20595 0t0 UDP *:1234
NetworkMa 1492 root 23u IPv4 25413 0t0 UDP 10.9.1.62:68->10.9.1.1:67
dnsmasq 1501 nobody 4u IPv4 20814 0t0 UDP 10.114.102.1:53
avahi-dae 26920 avahi 11u IPv4 234858 0t0 UDP *:5353
avahi-dae 26920 avahi 12u IPv6 234859 0t0 UDP *:5353
avahi-dae 26920 avahi 13u IPv4 234860 0t0 UDP *:59008
avahi-dae 26920 avahi 14u IPv6 234861 0t0 UDP *:59252
node 31752 root 22u IPv4 276415 0t0 UDP *:12345
node 31752 root 23u IPv4 276433 0t0 UDP *:12345 So, at a bare minimum you need to forward to TCP 8000 and 80, and UDP 12345. The only port conflict that I can see with the pihole project is 80, so you are on the right track. Now, in theory none of those ports actually need to be reachable from outside of the balena network, but I'm not 100% sure about that.
All of that said, changing from host to bridge mode should not prevent sound-supervisor from starting. I tried to test that here, but I can't get a successful push right now (Issue #462).
Once the device is loaded, what do you see in the logs when you manually try to start the service?
Philip-A
tmigone
Hello, I need your support for proper docker compose config, please. I am trying to merge multiple apps to run them on one device with balenaOS. Currently these are balena-sound and balena-pihole. I started with this article: https://www.balena.io/blog/two-projects-one-device-turn-your-raspberry-pi-into-a-multitool/
My goal is, that balena-sound does not use host port 80. How can I achieve that?
Question 1: Which service is using port 80? Following log message lets me think that
sound-supervisoris currently using port 80 (on host).Question 2: How can I make this service use another host port? Your checked-in docker-compose.yml uses following definition:
I am new to Docker, but in my opinion
network_mode: hostmeans that the definitionports: - 80:80is ignored, because the hosts network interface is used directly without any isolation.Therefore changing the port forwarding to
ports: - 8080:80did not the trick for me (in combination withnetwork_mode: host).sound-supervisoris still using port 80.Next, I tried to remove
network_mode: hostwith the goal that the container uses bridged network mode. But unfortunately, the service does not start in this mode. At least it looks like that for me, because of log messages like:But I don’t get any log message from
sound-supervisoritself, so I don’t know why the container is not coming up, yet.Then I searched the documentation for config parameters to change the web port
sound-supervisoris binding its web server or disable it completely, but I did not find any.I am surprised that nobody else seamed have this problem yet. Did I miss something obvious? I appreciate your help.