If you're new to Mesos
See the getting started page for more information about downloading, building, and deploying Mesos.
If you'd like to get involved or you're looking for support
See our community page for more details.
Mesos 1.0.0 introduced experimental support for Windows.
Install the latest Visual Studio 2017: The “Community” edition is sufficient (and free). During installation, choose the “Desktop development with C++” workload.
Install CMake 3.8.0 or later. During installation, choose to “Add CMake to the system PATH for all users”.
Install GNU patch for Windows.
If building from source, install Git. During installation, keep the defaults to “Use Git from the Windows Command Prompt”, and “Checkout Windows-style, commit Unix-style line endings” (i.e.
git config core.autocrlf true).
Make sure there are no spaces in your build directory. For example,
C:/Program Files (x86)/mesosis an invalid build directory.
If developing Mesos, install Python 2 (not Python 3), in order to use our support scripts (e.g. to post and apply patches, or lint source code).
Following are the instructions for Windows 10.
# Start an administrative session of PowerShell # (required for creating symlinks when using the agent). # Clone (or extract) Mesos. git clone https://git-wip-us.apache.org/repos/asf/mesos.git cd mesos # Configure using CMake for an out-of-tree build. mkdir build cd build cmake .. -G "Visual Studio 15 2017 Win64" -T "host=x64" -DENABLE_LIBEVENT=1 # Build Mesos. # To build just the Mesos agent, add `--target mesos-agent`. cmake --build . # The Windows agent exposes new isolators that must be used as with # the `--isolation` flag. To get started point the agent to a working # master, using eiher an IP address or zookeeper information. src\mesos-agent.exe --master=<master> --work_dir=<work folder> --launcher_dir=<repository>\build\src
The current implementation is known to have the following limitations:
- Only the agent should be run on Windows. The Mesos master can be launched, but only for testing as the master does not support high-availability setups on Windows.
- While Mesos supports NTFS long paths internally, tasks which do not support
long paths must be run on agent whose
--work_diris a short path.
- The Mesos agent must be run as Administrator, mainly due to symlinks.
MesosContainerizercurrently does not provide any actual resource isolation (similar to running the Mesos agent on POSIX).
For more information regarding the status of Windows support in Mesos, please refer to the JIRA epic.