--- title: minimesos 0.7.1 - Config file support and init command description: "Yesterday we released minimesos 0.7.1. You can install it using our new installer: curl -sSL https://minimesos.org/install | sh. The Docker images are available from Docker Hub and the jar is available via Jitpack." image: http://cdn2.hubspot.net/hubfs/2668666/All-InOne-2016/Image/bg-img.jpg --- Check out our **[Cloud Native Services](https://www.container-solutions.com/services) **and** **book a call with one of our experts today!  [![Container Solutions](https://blog.container-solutions.com/hubfs/CS_blog/logo-main.svg "Container Solutions")](http://container-solutions.com) - share: - [**](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fblog.container-solutions.com%2Fminimesos-0-7-0-config-file-support-init-command) - [**](https://www.twitter.com/share?url=https%3A%2F%2Fblog.container-solutions.com%2Fminimesos-0-7-0-config-file-support-init-command) - [**](http://www.linkedin.com/shareArticle?mini=true&url=https://blog.container-solutions.com/minimesos-0-7-0-config-file-support-init-command) - [**](https://blog.container-solutions.com/minimesos-0-7-0-config-file-support-init-command#) [![](http://cdn2.hubspot.net/hubfs/2668666/All-InOne-2016/Image/bg-img.jpg) ](https://blog.container-solutions.com/minimesos-0-7-0-config-file-support-init-command) [Docker](https://blog.container-solutions.com/tag/docker), [Microservices](https://blog.container-solutions.com/tag/microservices) # minimesos 0.7.1 - Config file support and init command [Frank Scholten](https://blog.container-solutions.com/author/frank-scholten) ![Frank Scholten](https://blog.container-solutions.com/hubfs/frank.jpg) March 16, 2016 3 minutes Read [![MiniMesos logo - Config file support and init command](https://blog.container-solutions.com/hs-fs/hubfs/Imported_Blog_Media/minimesos-1.png?width=150&height=129&name=minimesos-1.png)](https://blog.container-solutions.com/hubfs/Imported_Blog_Media/minimesos-1.png) Yesterday we released minimesos 0.7.1. You can install it using our new installer: `curl -sSL https://minimesos.org/install | sh`. The Docker images are available from [Docker Hub](https://hub.docker.com/r/containersol/minimesos/tags/) and the jar is available via [Jitpack](https://jitpack.io/#ContainerSolutions/minimesos). Minimesos is an experimentation and testing tool for Mesos with a Java API and a [Vagrant-like workflow](https://www.vagrantup.com/docs/cli/). The main new improvements in this release are the new [`minimesos init`](https://github.com/ContainerSolutions/minimesos/issues/255) command and the [minimesosFile](https://github.com/ContainerSolutions/minimesos/issues/185). Besides that we fixed a few issues surrounding image pulling and Mesos versions. # Configure your cluster with the minimesosFile In previous versions of minimesos, the `up` command created a default cluster consisting of a single Master, Agent and Zookeeper container. Several people wanted to change this configuration from the cli by changing Mesos versions or Agent resources. Therefore we introduced the `minimesosFile`. Additionally, we added the `minimesos init` command to generate a default configuration that can be changed before running `up`. Check out Viktor's ([@sadovnikov](https://twitter.com/sadovnikov)) video on the minimesos blog: [![minimesos init CLI command](https://static.hsstatic.net/BlogImporterAssetsUI/ex/missing-image.png)](https://minimesos.org/blog/minimesos-init/) # What's next? The focus of the next version of minimesos, 0.8.0 is [service discovery](https://en.wikipedia.org/wiki/Service_discovery). The goal is that frameworks and processes running on minimesos can find each other automatically. Currently, when installing a framework via Marathon it is necessary to put hardcoded IP addresses of the Zookeeper container in the JSON file. Our aim is to setup a standardized address for Zookeeper so this name can be used inside the Marathon JSON file. # Keep in touch Thanks for reading! Keep in touch by commenting on the blog or talk to us at [@minimesos](https://twitter.com/minimesos) and [@ContainerSoluti](https://twitter.com/Containersoluti). Check out the [open issues](https://github.com/containersolutions/mini-mesos/issues) on Github. Do you have an idea on how to improve minimesos? Please open an issue or add a PR at the [minimesos](https://github.com/containersolutions/mini-mesos) Github repo. We hope you find minimesos useful. See you next time! [### Cobbler in a Docker Container ](https://blog.container-solutions.com/cobbler-in-a-docker-container) [![prev-arrow](https://cdn2.hubspot.net/hubfs/3842749/Wow%202019/Images/left-arrow.png) Previous article](https://blog.container-solutions.com/cobbler-in-a-docker-container) [ Next article ![next-arrow](https://cdn2.hubspot.net/hubfs/3842749/Wow%202019/Images/right-arrow.png) ](https://blog.container-solutions.com/mesos-framework-overview) [ ### Mesos framework overview: Mesos-starter, MesosFramework, Kib... ](https://blog.container-solutions.com/mesos-framework-overview) Comments Leave your Comment ![cs-logo-white](https://blog.container-solutions.com/hs-fs/hubfs/cs-logo-white.png?width=150&height=61&name=cs-logo-white.png "cs-logo-white") #### **Talk to sales** [info@container-solutions.com](mailto:info@container-Solutions.com) #### Stay In Touch - [**](https://www.linkedin.com/company/container-solutions/) - [**](https://twitter.com/containersoluti) © 2024 Container Solutions