search

ContainerSolutions / minimesos

The experimentation and testing tool for Apache Mesos - NO LONGER MAINTANED!
https://www.minimesos.org
Apache License 2.0
427 stars 61 forks source link

should i be able to run minimesos on docker-4-mac? #441

Closed tony-kerz closed 8 years ago

tony-kerz commented 8 years ago

running docker for mac:

~/g/minimesos (master) $ docker --version
Docker version 1.11.1, build 5604cbe

minimesos up looks good:

~/g/minimesos (master) $ minimesos up
Minimesos cluster is running: 2200110749
Mesos version: 0.25
export MINIMESOS_NETWORK_GATEWAY=172.17.0.1
export MINIMESOS_AGENT=http://172.17.0.5:5051; export MINIMESOS_AGENT_IP=172.17.0.5
export MINIMESOS_ZOOKEEPER=zk://172.17.0.3:2181/mesos; export MINIMESOS_ZOOKEEPER_IP=172.17.0.3
export MINIMESOS_MARATHON=http://172.17.0.6:8080; export MINIMESOS_MARATHON_IP=172.17.0.6
export MINIMESOS_CONSUL=http://172.17.0.7:8500; export MINIMESOS_CONSUL_IP=172.17.0.7
export MINIMESOS_MASTER=http://172.17.0.4:5050; export MINIMESOS_MASTER_IP=172.17.0.4

looks like docker images are running:

~/g/minimesos (master) $ docker ps
CONTAINER ID        IMAGE                                                COMMAND                  CREATED              STATUS              PORTS                                                                          NAMES
65081890a86e        weaveworks/scope:0.13.1                              "/home/weave/entrypoi"   About a minute ago   Up About a minute                                                                                  mesos-bc47fbb2-7278-41c5-b543-613ca3e8e42b-S0.c6cf6925-0997-4c84-92d7-dd7114726de4
53d39ea356ae        gliderlabs/registrator:v6                            "/bin/registrator -in"   About a minute ago   Up About a minute                                                                                  minimesos-registrator-2200110749-352241034
6ff1171112bd        containersol/consul-server:0.6-1                     "/bin/consul agent -s"   2 minutes ago        Up 2 minutes        53/udp, 8300-8302/tcp, 8400/tcp, 8500/tcp, 8301-8302/udp, 8600/udp, 8600/tcp   minimesos-consul-2200110749-4059834184
6338b1c54cec        mesosphere/marathon:v0.15.3                          "./bin/start --master"   2 minutes ago        Up 2 minutes        8080/tcp                                                                       minimesos-marathon-2200110749-3561179087
9d022c03c430        containersol/mesos-agent:0.25.0-0.2.70.ubuntu1404    "/usr/local/bin/mesos"   3 minutes ago        Up 3 minutes        5051/tcp, 31000-32000/tcp                                                      minimesos-agent-2200110749-1783880163
cd025cb306a0        containersol/mesos-master:0.25.0-0.2.70.ubuntu1404   "mesos-master --regis"   3 minutes ago        Up 3 minutes        5050/tcp                                                                       minimesos-master-2200110749-1042239626
2fc5963da2fc        jplock/zookeeper:3.4.6                               "/opt/zookeeper/bin/z"   3 minutes ago        Up 3 minutes        2181/tcp, 2888/tcp, 3888/tcp                                                   minimesos-zookeeper-2200110749-1645289305

should i be able to ping the master for instance:

~/g/minimesos (master) $ ping 172.17.0.4
PING 172.17.0.4 (172.17.0.4): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1

i see this issue around docker-4-mac, but it seems to be focused on builds. would this issue prevent from just running under docker-4-mac as well?

any guidance appreciated!

adam-sandor commented 8 years ago

Hi @tony-kerz,

I just bumped into this one the other day too. It seems that currently there is no way to route traffic to container IPs when using the docker-4-mac unfortunately. I have switched back to docker-machine for the time being. See this forum thread: https://forums.docker.com/t/ip-routing-to-container/8424/5

tony-kerz commented 8 years ago

roger that adam, i'll use docker-machine for now as well. u can decide whether to leave this issue open as a placeholder until the docker team decides how to remedy.

adam-sandor commented 8 years ago

Let’s keep it open and I’ll check what’s going on with docker-4-mac regularly. I’d like to see this one working asap, it was a disappointment having to go back to docker-machine…

On 19 May 2016, at 16:46, tony kerz notifications@github.com wrote:

roger that adam, i'll use docker-machine for now as well. u can decide whether to leave this issue open as a placeholder until the docker team decides how to remedy.

— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/ContainerSolutions/minimesos/issues/441#issuecomment-220346746

frankscholten commented 8 years ago

See https://github.com/ContainerSolutions/minimesos/issues/431

frankscholten commented 8 years ago

Closing. Blocks on https://github.com/ContainerSolutions/minimesos/issues/431 because of a limitation on docker-java.