Hey @dagrooms52,
It appears that this may be caused by the change to DNSMasq or possibly the update to docker 17.03, and that we haven’t tested dind since this was added.
We run host networking to containers by default, so the wiping iptable rules also has the nasty knock-on effect which stops the supervisor from being able to request update images (and probably more).
It should be possible to get create and use another network bridge as explained here: https://stackoverflow.com/questions/32334167/is-it-possible-to-start-multiple-docker-daemons-on-the-same-machine/34058675#34058675 but I haven’t had any luck so far, I’m posting it here incase you have a chance to try it before I have another go at it.
This looks to be a dupe of Updated docker-compose support, if you agree let’s close this and track it in that thread?