#The optimal debug tool depends on the
1 messages ยท Page 1 of 1 (latest)
The fun part is that you're right, HA can't connect to the Echo
Unforuantley, I am going to have to spend time figuring out to put HA on the host network and while also having services on my custom bridge network be accessible to HA
It's much simpler than you think. Do you have a docker-compose file with the HA container? Or are you just running it from CLI?
@craggy current I'll have to put the hass service on the host network, but it would mean it will lose access to my automation docker network
Do you have a suggestion on how this may work otherwise?
something like
services:
hass:
networks:
automation:
...
host_network:
networks:
host_network:
external: true
name: host
but you have to create a network named host (which Docker links automatically)
https://docs.docker.com/compose/compose-file/compose-file-v3/#host-or-none
Unforunatley, I am getting network-scoped alias is supported only for containers in user defined networks with the above
I am pretty sure I cannot mix-match a bridge and host network
this is a bit above my pay grade ๐ search the interwebz and see what solutions you may find, then please post them back for others to benefit
Yep, Docker docs say the same:
Use the host's networking stack, or no networking. Equivalent to docker run --net=host or docker run --net=none. Only used if you use docker stack commands. If you use the docker-compose command, use network_mode instead.
If you use compose, use network_mode. Guess like I got some configuring to do ๐ฆ
Did a bit of magic and did the following:
- Moved HA into host networking
- Left all other services in the Docker network
- Add the "127.0.0.1:XXXXX:YYYYYY" (where XXXX is the port to expose to the host network and YYYY is the container network
- Attached all services in HA as if they were on localhost/127.0.0.1
This got my Atom work ๐
Thanks for pointing me in the right direction @craggy current !!!