#Docker ip resolution between stacks install#
#Docker ip resolution between stacks update#

Two containers deployed from one yml file will place them on the same (custom) network. It looks like I messed up DNS for all newly created containers but have no idea where to check this. But again: Why could the db container not resolve itself via localhost? Layer 2 and Layer 3 is not clear to me, maybe a container has no ip address in that particular network? But what could prevent that? At least the db container I'd like to reach is connected to the newly created network and has an ip address (I checked this in the Portainer gui) and so should be reachable by the webserver container. Is there another reason why a container will not be able to reach another? In 'real life' basic network troubleshooting you would first look for layer 1 which is indisputably present here. What I don't understand: Is there any configuration inside docker that prevents docker containers in the same network to reach each other? Let's call it a docker 'firewall' setting or something similar? I have no clue where this could make sense but this could explain my issues. Each container for a service joins the default network and is both reachable by other containers on that network, and discoverable by them at a hostname identical to the container name.

#Docker ip resolution between stacks install#

In the meanwhile my portainer and a watchtower instance are running fine on the system bridge network and at least watchtower is able to lookup hosts in the internet as it sends mail and pulls new images as it should.īefore I throw away my current setup and start with a clean install I'd like to send an SOS to the community: Has anyone an idea where to look for the root cause?īy default Compose sets up a single network for your app.

#Docker ip resolution between stacks update#

I've had a comparable problem while testing a mayan edms docker instance: The instance was running fine but was unable to resolve the mayan-homepage for it's integrated update check mechanism. Do anyone know about any incompatibility between portainer and docker-compose? Or does anyone have an idea where to dig into that issue? I'm googling around for a couple of days but unfortunately, I'm obviously not hitting the right search string. It seems like my docker installation doesn't allow any dns-lookups at all for container in a bridge network and I have no idea why. I tried to setup that stuff with docker compose, following the installation guide.Īfter creating the container with the docker-compose up -d command, the webserver-container states could not translate host name 'db' to address: Temporary failure in name resolution and even the db-container is in state could not resolve 'localhost': Temporary failure in name resolution. Please allow me to describe the issue in some words: When creating docker container for the document management systems paperless-ng the webserver-container is unable to resolve the other containers. I'm currently getting sane about an issue in docker on openmediavault and I can't find any solution by myself.