Running services in container enrironments often leads to the need enabling access from one conteiner to another. This is quiet easy, if we are runnung all containers in the same docker net. If the containers running in different networks, we have to access the other container by connecting the exposed port on the host. While instancing the container, we create an entry in the docker internal address solution to refere to the host.<\/p>\n Or within Problem Running services in container enrironments often leads to the need enabling access from one conteiner to another. This is quiet easy, if we are runnung all containers in the same docker net. If the containers running in different networks, we have to access the other container by connecting the exposed port on the host. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-virtualisierung"],"_links":{"self":[{"href":"https:\/\/trashdump.net\/index.php?rest_route=\/wp\/v2\/posts\/125"}],"collection":[{"href":"https:\/\/trashdump.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trashdump.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trashdump.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/trashdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=125"}],"version-history":[{"count":3,"href":"https:\/\/trashdump.net\/index.php?rest_route=\/wp\/v2\/posts\/125\/revisions"}],"predecessor-version":[{"id":148,"href":"https:\/\/trashdump.net\/index.php?rest_route=\/wp\/v2\/posts\/125\/revisions\/148"}],"wp:attachment":[{"href":"https:\/\/trashdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trashdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trashdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nSince we are running in a container localhost<\/em> is refering to the container itself. In the first it seems simple to connect to IP or hostname of the host in its LAN, but this is not very flexible. If the host gets another IP oder the container moves to another system, the config allways has to be adopted.<\/p>\nPossible Solution<\/h2>\n
docker run -d \\\n --restart: always \\\n --add-host host.docker.internal:host-gateway \\\n alpine:latest\n<\/code><\/pre>\n
\n“`docker-compose.yaml“` …<\/p>\n...\nservices:\n my_host:\n restart: always\n image: alpine:latest\n extra_hosts:\n - host.docker.internal:host-gateway\n...\n<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"