I've seen some suggestions, like creating a Linux-specific config file ( docs), but the solution a co-worker of mine came up with seems more elegant and less complex to me. But I got you covered, there's an easy approach to make this work. On Docker for Linux, the IP address of the gateway between the Docker host and the bridge network is 172.17.0.1 if you are using default networking.ĭo you see the problem already? They are different, so you cannot simply run docker-compose up -d and all operating systems behave the same. This is for development purpose and will not work in a production environment outside of Docker Desktop for Mac/Windows. From 18.03 onwards our recommendation is to connect to the special DNS name, which resolves to the internal IP address used by the host. The host has a changing IP address (or none if you have no network access). It explains the required prerequisites to make sure docker has access to a host disk. Problem The install Home Assistant in docker on Windows instructions are great, with one exception. Linuxįor macOS and Windows the following special DNS name can be used: I hope that youve landed here before spending hours/days trying to find a solution as to why you cant forward the Home Assistant port in Docker. I'll show you how to easily make this work simultaneously for macOS, Windows, and Linux - because their docker networking settings differ.ĭocker Networking on macOS and Windows vs. Debugging or reverse proxies running on your host are two additional example use-cases. For instance, you need to be able to connect to the host network from inside a Docker container to access your app or database running locally on the host. Once in a while, you may need your Docker host's IP address.
0 kommentar(er)
