You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker daemon seems to dynamically allocate IP address for docker0 bridge. In my case I had 172.18.0.1 allocated causing Bluetooth audio to stop working among other things.
Setting bip: "172.17.0.1/16" in /etc/docker/daemon.json and restarting machine fixes the issue
I would advise giving up the bridge altogether for hifiberry. Just use host network stack for containers and disable docker0 altogether. I don't see any benefit of using the bridge for multimedia application like Hifiberry
This would also fix #525 and other similar issues.
The text was updated successfully, but these errors were encountered:
Describe the bug
Docker daemon seems to dynamically allocate IP address for docker0 bridge. In my case I had 172.18.0.1 allocated causing Bluetooth audio to stop working among other things.
It looks like 172.17.0.1 IP address is hardcoded in several components https://github.com/hifiberry/alsaloop/blob/master/alsaloop.py#L93
HiFiBerryOS version
20240523
Raspberry Pi 3+
HiFiBerry sound card
DAC2 HD
To Reproduce
I am not sure how to reproduce this
Expected behavior
I expected everything to work OOB
Additional context
Setting
bip: "172.17.0.1/16"
in/etc/docker/daemon.json
and restarting machine fixes the issueI would advise giving up the bridge altogether for hifiberry. Just use host network stack for containers and disable
docker0
altogether. I don't see any benefit of using the bridge for multimedia application like HifiberryThis would also fix #525 and other similar issues.
The text was updated successfully, but these errors were encountered: