> On Nov. 16, 2017, 6:43 p.m., Andrew Schwartzmeyer wrote: > > src/docker/docker.cpp > > Lines 742-743 (original), 742-760 (patched) > > <https://reviews.apache.org/r/63860/diff/1/?file=1893972#file1893972line742> > > > > If there's an MSDN doc we can reference here to explain this mapping, > > that'd be great.
There isn't a doc that says they are similar, but you can infer that from the docs. I can provide a link to the MSDN Windows container networking docs that describe how nat works. - Akash ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63860/#review191217 ----------------------------------------------------------- On Nov. 16, 2017, 6:18 p.m., Akash Gupta wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/63860/ > ----------------------------------------------------------- > > (Updated Nov. 16, 2017, 6:18 p.m.) > > > Review request for mesos, Andrew Schwartzmeyer and John Kordich. > > > Bugs: MESOS-7342 > https://issues.apache.org/jira/browse/MESOS-7342 > > > Repository: mesos > > > Description > ------- > > The current Network enum in DockerInfo is specific to Linux containers. > Instead of supporting {host, bridge, none, user} networks, Windows > docker supports {nat, none, user} networks. Now, if the host network > type is sent to the Windows agent, it will return an error. If the > bridge network is sent, then it will be internally converted to nat, > since they are equivalent. > > > Diffs > ----- > > src/docker/docker.cpp 722a54ad113fc4e2bb22a8f08e307ab38d5fbfed > > > Diff: https://reviews.apache.org/r/63860/diff/1/ > > > Testing > ------- > > See https://reviews.apache.org/r/63862/ for test results. > > > Thanks, > > Akash Gupta > >
