Need help with vagrant-mesos?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

124 Stars 36 Forks 38 Commits 5 Opened issues


Mesos/Docker/Marathon/Aurora development Vagrant Virtualbox setup

Services available


Need anything else?

Contributors list

# 375,056
36 commits
# 256,789
1 commit


Vagrant dev environent setup with Mesos/Marathon/Chronos/Aurora/Jenkins/Docker

Disclaimer: This Vagrant setup consumes significant resources but runs fine on my 2013 Macbook Pro developer notebook with a 2.8 GHz Intel Core i7 processor and 16 GB RAM. It may not work as well on a machine with lesser hardware specs.

Vagrant Setup


Run the following script which will launch 3 VMs each with all the components shown in the graphic above installed. To save time the script will install everything on the first VM, save it as a vbox image and then clone the remaining VMs from it.

$ ./

Mesos master instance

mesos1 ip address:

The main instance has the following services actively running upon startup and has 4GB allocated RAM:

1. Mesos master
2. Mesos slave
3. Zookeeper
4. Docker
5. Docker Executor
6. Jenkins
7. Marathon
8. Aurora
9. Chronos

Additional VMs

Your cluster now effectively has 3 Mesos masters, 3 zookeepers and 3 Mesos slaves (each with Docker installed). Jenkins, Marathon, Chronos & Aurora are installed on the additional VMs too except that they have been disabled on startup. The additional Mesos instances have been allocated a lesser 2GB RAM each.

mesos2 ip address:
mesos3 ip address:

Each additional VM with the following services actively running upon startup:

1. Mesos master
2. Mesos slave
3. Zookeeper
4. Docker

SSH Access

ssh [email protected] | ssh [email protected] | ssh [email protected]

Root SSH Credentials:

username: root
password: vagrant


Create these entries in the /etc/hosts file on the host machine for quick access to the VMs.  mesos1 jenkins1 marathon1 aurora1 chronos1  mesos2 jenkins2 marathon2 aurora2 chronos2  mesos3 jenkins3 marathon3 aurora3 chronos3

An Nginx HTTP proxy server is running on each machine so that you can access the applications on the respective VMs. Only one Mesos master is active at a time so you will be immediately redirected to the leading master.

Mesos - http://mesos1 | http://mesos2 | http://mesos3

Accessing the Jenkins web UI:


Accessing the Marathon web UI


Accessing the Aurora web UI


Accessing the Chronos web UI


Destroying VMs

Run the following script to destroy the VMs


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.