I am using a nginx proxy for access into other containers accessed via the container name. This works fine. One of the containers that nginx forwards to is in the host network. I used to be able to access that one via 172.17.0.1. This no longer works. E.g. ping 172.17.0.1 fails. On devices runn…

Hi ttmetro, You might want to check Balena Services Masterclass - Balena Documentation for setting up multi service networking. Also you might want to try proxy pass to set up forwarding for nginx ( NGINX Reverse Proxy | NGINX Plus ).

Hi Ja-Ilija, As far as I understand, service micropython must use network_mode: host to access bluetooth. All other services including nginx run in the default Docker bridge. The problem is that nginx can no longer proxy traffic to micropython. proxy_pass http://172.17.0.1:8888; use…

Hi there, From what you have described, it seems like in the past, you were able to access the micropython service port 8888 from inside a bridge networking service by accessing the docker engine host at 172.17.0.1. The 172.x.x.x addresses are given to the services on the docker bridge network, wit…

Hi Rcooke, You are right on - the address of the host network apparently changed to 172.19.0.1. I agree that running “MicroPython” in the bridge net would make more safe. Have you found out how to access Bluetooth in that case? Separately, it would also make sense if there was a “standard” and re…

you may want to try the device url. in this way you kind of insure that it won’t change. If you don’t want to make the device visible you may use the api to get the api and dynamically set it up Interacting with the balena Supervisor - Balena Documentation .

Hi, following up on this, did the solution suggested in the forum post provided by my colleague above worked for your use case? This was to extract the ip address with: ip route | awk '/br-/ { print $7 }' | head -n 1

This works - with a slight modification: ip route | awk '{print $3}' | head -n 1 Output from ip route - perhaps this differs from system to system? default via 172.19.0.1 dev eth0 10.114.104.0/25 dev eth1 scope link src 10.114.104.3 172.19.0.0/16 dev eth0 scope link src 172.19.0.8

access host network

General

maggie0002 June 6, 2022, 8:39pm 13

This forum thread may be helpful too: Default bridge IP for Intel NUC is missing - #5 by Maggie

Topic		Replies	Views
Reaching other container with network_mode host balenaOS	17	11016	December 23, 2020
How to address (IP or hostname) of other container with network_mode : host? (* FIXED *) balenaOS network	1	3077	March 20, 2019
docker compose network mode host balenaOS	1	1594	September 30, 2020
Unable to connect service to host network and other services Product support	5	1019	July 18, 2019
Unable to connect to host mode container from bridged mode container balenaEngine	1	449	March 21, 2019

access host network

Related topics