Thanks to everyone for the considered replies, both on- and off-list! Folks tossed out a number of creative ideas for wiring things up a little differently, kind of outside of the Docker tools. At one extreme, one could do Docker deployment differently -- in effect, doing lots of the bits by hand, whether with managing the containers & their deployment, making explicit changes to network config, and so on.
At the other extreme would be a solution that supported the promise of these tools (like docker-machine & docker-compose), namely, that they take care of all of this stuff so that you never have to think about it. ;) Maybe the ultimate solution is something like a fix to docker-machine that lets it understand the Direct Connect / RFC1918 context, perhaps via a flag when invoked, or something similar. A lot to chew on...I will digest... Thanks! -Greg
------------------------------------------------------------------------- The following was automatically added to this message by the list server: To learn more about Micronet, including how to subscribe to or unsubscribe from its mailing list and how to find out about upcoming meetings, please visit the Micronet Web site: http://micronet.berkeley.edu Messages you send to this mailing list are public and world-viewable, and the list's archives can be browsed and searched on the Internet. This means these messages can be viewed by (among others) your bosses, prospective employers, and people who have known you in the past. ANNOUNCEMENTS: To send announcements to the Micronet list, please use the micronet-annou...@lists.berkeley.edu list.
