[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228202#comment-14228202 ] Ryan Thomas commented on MESOS-1563: Hi Ian, Did you manage to dig up the branch? > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1925) Docker kill does not allow containers to exit gracefully
[ https://issues.apache.org/jira/browse/MESOS-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190216#comment-14190216 ] Ryan Thomas commented on MESOS-1925: [~tnachen] is there anything more to do in order to get this patch merged? > Docker kill does not allow containers to exit gracefully > > > Key: MESOS-1925 > URL: https://issues.apache.org/jira/browse/MESOS-1925 > Project: Mesos > Issue Type: Improvement > Components: containerization >Affects Versions: 0.20.1 >Reporter: Ryan Thomas >Assignee: Timothy Chen > > The docker implementation uses the docker kill command, this immediately > terminated the container, not allowing it to exit gracefully. > We should be using the docker stop command that will send a kill after a > predetermined amount of time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1925) Docker kill does not allow containers to exit gracefully
[ https://issues.apache.org/jira/browse/MESOS-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171600#comment-14171600 ] Ryan Thomas commented on MESOS-1925: Patch here: https://reviews.apache.org/r/26709/ > Docker kill does not allow containers to exit gracefully > > > Key: MESOS-1925 > URL: https://issues.apache.org/jira/browse/MESOS-1925 > Project: Mesos > Issue Type: Improvement > Components: containerization >Affects Versions: 0.20.1 >Reporter: Ryan Thomas > > The docker implementation uses the docker kill command, this immediately > terminated the container, not allowing it to exit gracefully. > We should be using the docker stop command that will send a kill after a > predetermined amount of time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-1925) Docker kill does not allow containers to exit gracefully
[ https://issues.apache.org/jira/browse/MESOS-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171593#comment-14171593 ] Ryan Thomas commented on MESOS-1925: Thanks. I went with just a 30 second timeout for the stop (the default is 10) - though I think some time in the future we may want to make this configurable. > Docker kill does not allow containers to exit gracefully > > > Key: MESOS-1925 > URL: https://issues.apache.org/jira/browse/MESOS-1925 > Project: Mesos > Issue Type: Improvement > Components: containerization >Affects Versions: 0.20.1 >Reporter: Ryan Thomas > > The docker implementation uses the docker kill command, this immediately > terminated the container, not allowing it to exit gracefully. > We should be using the docker stop command that will send a kill after a > predetermined amount of time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-809) External control of the ip that Mesos components publish to zookeeper
[
https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106949#comment-14106949
]
Ryan Thomas edited comment on MESOS-809 at 8/22/14 8:08 PM:
As a work-around for this in docker you can use bridged network mode by adding
the bridge to the daemon, or by using the {{--net=host}} argument for the
{{docker run}} command.
was (Author: ryant):
As a work-around for this in docker you can use bridged network mode.
> External control of the ip that Mesos components publish to zookeeper
> -
>
> Key: MESOS-809
> URL: https://issues.apache.org/jira/browse/MESOS-809
> Project: Mesos
> Issue Type: Improvement
> Components: framework, master, slave
>Affects Versions: 0.14.2
>Reporter: Khalid Goudeaux
>Priority: Minor
>
> With tools like Docker making containers more manageable, it's tempting to
> use containers for all software installation. The CoreOS project is an
> example of this.
> When an application is run inside a container it sees a different ip/hostname
> from the host system running the container. That ip is only valid from inside
> that host, no other machine can see it.
> From inside a container, the Mesos master and slave publish that private ip
> to zookeeper and as a result they can't find each other if they're on
> different machines. The --ip option can't help because the public ip isn't
> available for binding from within a container.
> Essentially, from inside the container, mesos processes don't know the ip
> they're available at (they may not know the port either).
> It would be nice to bootstrap the processes with the correct ip for them to
> publish to zookeeper.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (MESOS-809) External control of the ip that Mesos components publish to zookeeper
[ https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106949#comment-14106949 ] Ryan Thomas commented on MESOS-809: --- As a work-around for this in docker you can use bridged network mode. > External control of the ip that Mesos components publish to zookeeper > - > > Key: MESOS-809 > URL: https://issues.apache.org/jira/browse/MESOS-809 > Project: Mesos > Issue Type: Improvement > Components: framework, master, slave >Affects Versions: 0.14.2 >Reporter: Khalid Goudeaux >Priority: Minor > > With tools like Docker making containers more manageable, it's tempting to > use containers for all software installation. The CoreOS project is an > example of this. > When an application is run inside a container it sees a different ip/hostname > from the host system running the container. That ip is only valid from inside > that host, no other machine can see it. > From inside a container, the Mesos master and slave publish that private ip > to zookeeper and as a result they can't find each other if they're on > different machines. The --ip option can't help because the public ip isn't > available for binding from within a container. > Essentially, from inside the container, mesos processes don't know the ip > they're available at (they may not know the port either). > It would be nice to bootstrap the processes with the correct ip for them to > publish to zookeeper. -- This message was sent by Atlassian JIRA (v6.2#6252)
