I'd advise using Interlock image
ehazlett/interlock:1.2.0 and labeling your service containers with
mynetwork is the name of your overlay network. Also, don't publish the ports on your service containers, it's enough to just
You can see a full example of it being used in https://github.com/everett-toews/interlock-example
But please ignore the service1/service2 and
interlock.ext.service.name stuff in that example! That's experimental stuff based on this PR that hasn't made it into the
ehazlett/interlock upstream image yet.