Hi All,
One of the most used networking mode when users run containers using the
`DockerContainerizer` is docker bridge mode networking. In this mode
containers run in an isolator private address space, and services on the
container are exposed to the outside world using DNAT.
As we move towards
I pushed your patch, thanks!
On Fri, Aug 5, 2016 at 12:28 PM, Charles Allen <
charles.al...@metamarkets.com> wrote:
> https://reviews.apache.org/r/50862/ which is a proposed fix for MESOS-5929
> needs a shepherd. Is anyone able to do that?
>
https://reviews.apache.org/r/50862/ which is a proposed fix for MESOS-5929
needs a shepherd. Is anyone able to do that?
Created a patch https://reviews.apache.org/r/50851/
Looking for shepherd.
pt., 5.08.2016 o 09:49 użytkownik Tomek Janiszewski
napisał:
> I reported issue for this https://issues.apache.org/jira/browse/MESOS-5995
>
> pt., 5.08.2016 o 02:35 użytkownik Joseph Wu
Hi,
As you can see in MESOS-5917, I made sure that all the processes I could
find specify a distinguishable IDs.
After talking to Alex R and Ben M, I enforced the following naming schema:
For processes created by Mesos:
- Every process must specify a distinguishable process ID.
- The
I reported issue for this https://issues.apache.org/jira/browse/MESOS-5995
pt., 5.08.2016 o 02:35 użytkownik Joseph Wu napisał:
> This is not necessarily a bug, but I think we can safely extend our parsing
> code to handle this case.
>
> This is the method that would need