Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable Docker bridge #599

Open
laurivosandi opened this issue Mar 11, 2025 · 0 comments
Open

Disable Docker bridge #599

laurivosandi opened this issue Mar 11, 2025 · 0 comments

Comments

@laurivosandi
Copy link

laurivosandi commented Mar 11, 2025

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 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant