Service Stack Networks #20
Description
When spinning up a new service stack it creates a default network for your stack and the IPs allocated to that stack are for internal use only. If you need access outside of the stack it utilizes the docker_gwbridge (by default the 172.18.x.x network) which is a separate interface in the container but it is an interface that is not represented in the docker inspect command. This has me in a situation where I can get my traffic to the iam-proxy container but it fails with the error:
2017-03-30T15:53:00Z [http] Unable to find credentials path=/latest/meta-data/iam/security-credentials/my-role method=GET remoteAddr=172.18.0.4:49468 error="Unable to find container for IP: 172.18.0.4"
Does the service stack network model break iam-proxy beyond repair, or at least without a change to docker itself? Is there a means of tying the meta-data request back to the container without using IP? I don't immediately see a way but I was hoping you guys have given it some thought.