TrustRadius Insights
Docker has proven to be a versatile tool with a wide range of use cases. Users have found that Docker simplifies the packaging and …
Starting at $500 per year per node
View PricingOverview
What is Mirantis Kubernetes Engine?
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters…
Recent Reviews
Pricing
Free
$0.00
Cloud
per year
Basic
$500.00
Cloud
per year
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://store.mirantis.com
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $500 per year per node
Product Details
- About
- Tech Details
- FAQs
What is Mirantis Kubernetes Engine?
Mirantis Kubernetes Engine Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Frequently Asked Questions
The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
Mirantis Kubernetes Engine starts at $500.
Reviewers rate Support Rating highest, with a score of 7.8.
The most common users of Mirantis Kubernetes Engine are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(210)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Recommendations
Docker has proven to be a versatile tool with a wide range of use cases. Users have found that Docker simplifies the packaging and deployment of applications and services, allowing developers to match their development environment to production and eliminate cross-cutting software dependencies. It has been utilized as the backbone of a hosted app infrastructure, where every element is broken down into microservices deployed on the AWS cloud. Additionally, Docker has been instrumental in creating specialized microservices such as a Selenium Grid for automated web-based testing.
Moreover, Docker has played a crucial role in maintaining environmental consistency and streamlining deployment processes. It has enabled users to swiftly containerize Continuous Deployment and Integration pipelines, facilitating easy deployment and updates of the system and its environments. With Docker, users have been able to quickly deploy and monitor servers, firewalls, switches, and other components, providing a consistent and efficient environment for prototyping and testing. Another notable use case is spinning up new databases for microservices using Docker, ensuring consistency and independence across different environments.
Furthermore, Docker has integrated seamlessly with orchestration frameworks like Apache Mesos and Mesosphere Marathon. This combination has allowed for more efficient application development and deployment through effective management of containers. Docker has also demonstrated its utility in building server deployment files and running tests, enabling consistent deployments and reliable testing procedures.
In addition to these technical applications, Docker has proved to be valuable in hosting MySQL databases for production websites. Its stability, security features, and easy provisioning of identical instances have made it a preferred choice for users. Moreover, Docker has been extensively used in CI builds as it enables the creation of custom Linux images and seamless deployment of the latest code from the Docker registry.
The flexibility offered by Docker comes to the forefront when it comes to testing practices. It provides a highly configurable environment that makes cross-platform testing significantly more efficient. Users have leveraged Docker for both automated website/application testing pipelines as well as creating flexible environments for manual testing. Moreover, Docker has acted as a viable alternative to custom build and deploy solutions, offering a more flexible and decentralized process.
Notably, Docker has been embraced by a large global financial services provider to enhance efficiency and agility in application development. This adoption has resulted in increased innovation and productivity within the organization. Another significant benefit of using Docker is its ability to provide identical application environments across multiple deployment environments, leading to the deployment of more stable applications.
Furthermore, Docker has played a role in differentiating between server/compute infrastructure and application infrastructure. Operations teams can efficiently manage the cluster of servers, while application developers can run containers on the cluster, ensuring a clear separation and easier management of the two layers.
Teams have leveraged Docker for various development and deployment practices. Engineers can build applications in the same environment, eliminating local configuration issues that often arise when working across different setups. Docker has been particularly useful for WordPress development, replacing tools like Vagrant and providing tighter integration with Windows Hyper-V and better performance.
One of the significant advantages of Docker is its ability to containerize applications, resulting in consistent deployment environments across different stages and compatibility with various cloud platforms. This has greatly simplified the deployment process for users and enhanced their productivity. Additionally, Docker has been highly beneficial for the development team in resolving issues related to different setups on Windows, Linux, and Mac operating systems, while also providing easy configurations for automation QA.
Docker's impact extends beyond software development into the realm of research reproducibility. Users have developed Docker containers to encapsulate research pipelines, leveraging GitHub and DockerHub as public repositories. This approach has effectively addressed the challenge of ensuring reproducibility in research experiments.
Moreover, Docker Swarm has been employed to deploy internal applications in a managed cluster, successfully tackling scaling and load balancing issues during peak business hours. The combination of Docker with Kubernetes has also gained popularity among teams for containerizing projects and facilitating the development of microservices.
Overall, Docker's value proposition lies in its ability to provide consistent development environments, prevent deployment issues, streamline configurations, enhance testing efficiency, and simplify the overall software packaging and deployment processes. Its widespread usage across various industries highlights its robustness, ease of setup, community support through open-sourced images, and its ability to create and test configurations as needed. Docker has become an indispensable tool for many organizations seeking to optimize their software development lifecycle while improving productivity and innovation.
Based on the reviews, here are the three most common recommendations:
-
Users recommend trying Docker for deploying web services and running micro-services. They suggest doing tutorials to learn how to create Dockerfiles and docker-compose files correctly. Additionally, they advise considering whether Docker is necessary or if statically linked binaries can be used instead.
-
Users also recommend using Docker for QA environments and setting up developers with the environment they need. They find Docker to be an easy-to-use development tool with great rewards for a small amount of effort. However, some users caution that while Docker is a good solution, there may be better alternatives available.
-
Another common recommendation is to carefully consider the use of Docker in a workflow and discuss its usability within the organization before implementing it. Users emphasize the importance of learning the basics of Docker and understanding if continuous integration/deployment is the right approach. They also mention that Docker has a supportive community and is widely used in the industry.
Overall, users suggest experimenting with Docker, especially for new applications or running micro-services. They recommend taking advantage of Docker's simplicity and portability while being mindful of specific requirements and considering other options if needed.
Attribute Ratings
Reviews
(26-37 of 37)Companies can't remove reviews or game the system. Here's why
April 05, 2017
Docker - LEGOs for System Admins
Docker allows us to provision identical instances across our various systems (testing, staging, production, etc.). Docker has also allowed us to drastically reduce our spin up time for new instances, as all of the components that we commonly use have been converted into Docker Files.
Additionally, because of the great community behind Docker, many of the components that we use (MySQL, Tomcat, etc.) already have Docker files for them, many of which are awesome, and are easily adaptable (if necessary) to best suit the needs of our department.
Additionally, because of the great community behind Docker, many of the components that we use (MySQL, Tomcat, etc.) already have Docker files for them, many of which are awesome, and are easily adaptable (if necessary) to best suit the needs of our department.
- Easy to understand, with excellent documentation and community support.
- Easy to deploy to a variety of platforms.
- Allows for containers to be quickly be built, destroyed, transferred, all while keeping them consistent.
- Docker files can be limiting, because of the core idea of Docker, with only one process per container.
- Debugging DockerFiles can be a nightmare.
- Some configurations for a container cannot be updated post creation.
- There can be some trial-and-error associated with deploying containers and their corresponding Docker files.
April 03, 2017
Docker is for microservices and app delivery
We are using Docker today to spread multiple Tomcat instances across a single machine. Docker is currently being used by our devops team but we're a small company so that's pretty much the entire infrastructure team as well. Docker helps us keep our configs simple, easy to use, and reproducible in a really efficient manner.
- Docker makes it very easy to reproduce a service build and configuration. This is huge for rolling out quickly and efficiently.
- Docker can orchestrate your containers to auto scale up and down with Docker Compose. This is very useful on cloud providers where you pay for instance to keep prices down.
- Docker's intra-container networking works well for the most part but it does leave something to be desired when attempting to weave a complex deployment of microservices across multiple bare metal machines and networks. It would be nice to introduce some sort of modeling tool into container networking.
- A really neat feature for Docker could be to have an option to analyze container utilization and alert or notify on suggestions to improve efficiency.
March 24, 2017
Docker rocks!
We are just beginning to use Docker for some specialized microservices within our existing server infrastructure. Specifically, we use it to run a Selenium Grid for automated web-based testing. We are considering broader adoption of Docker within areas such as Java application deployment, local development environments, and continuous integration. Docker primarily helps us maintain environmental consistency (having the same environment from local development to deployment in the cloud).
- abstracting the virtualization aspects so that I don't need to know every detail (even to the point of not needing to know if Docker is using a VM behind the scenes or not)
- providing a simple yet powerful configuration scheme
- huge selection of base containers and easy way to derive from them
- automated builds through Docker Hub
- multiple configuration file versions can be a little confusing
- experienced some downtime with Docker Hub, though it was cleared up quickly
- not really a con of Docker, but it takes some time to learn the concepts of containers and adapt to that way of thinking. Perhaps it would be helpful to have a "Docker for Old School Sys Admins" guide that helps explain some of the differences in concepts and execution when working with containers.
March 07, 2017
Improves Environmental Consistency and Runtime Security
Docker is transforming our confidence in build and release as well as developer onboarding. Docker containerization finally is fulfilling the promise that Chef never did, giving us environmental consistency across developers, build, various environments and production. We've been eliminating deployment time errors by encapsulating the entire operating system, language core components, security patches, etc., into the application build time. This has reduced the complexity of getting developers up and running. No longer do developers and operations have to understand the full workings of the dependencies within an application in order to run and deploy it--instead, we only need to know how to get Docker running and deployed to get our applications up and running. This allows us to have truly ephemeral environments and dependency management and eases autoscaling.
- Environment consistency via full application and operating system encapsulation
- Securing software runtime by ensuring that the whole environment is easily and quickly discarded and re-run from a known good state--as well as putting all dependencies of the operating system and patches into the built artifact
- Easing developer setup time (up and running immediately without installing various software dependencies and configuring ports/etc.)
- The ecosystem has many minimal base images for software but this could use more focus on secure base images
- Many useful Docker commands are not built in as shortcuts to the CLI, but instead need to be managed as other aliases (e.g. `docker rm $(docker ps -a)` to remove all running and stopped containers)
- It's not always easy for people to optimize the caching layers of docker images--an auditing tool that suggests the order of Dockerfile commands for cache optimization would be handy
February 27, 2017
Docker killed the sysadmin, but it did not kill the developer
Docker is being used primarily to host a MySQL database that runs a production website. It has been very stable and easy to work with, and we like the security that containerization affords.
- Security by isolation.
- Ease of deployment.
- Flexible configuration.
- Scalability.
- Resource management.
- Administration simplicity.
February 20, 2017
Docker for development is really amazing
We're using Docker with Apache Mesos and Mesosphere Marathon for orchestration. Many departments are using it to develop and deploy applications.
- Docker is really good to develop applications in an isolated environment
- Compose different services to make your application infrastructure
- Docker uses a daemon. This is a single point of failure for an infrastructure that provides many containers. If you need to restart this daemon, you will lose all your containers.
February 15, 2017
Simple Up and Running Script Based Containerization
We use Docker to provide us fast containerization of our Continuous Deployment and Integration pipelines. Once our code is good for shipping, we trigger a test pipeline which will in turn compile all its dockerfiles, upload them to hub.docker.com if needed and then upload/install an updated version of the system and its environments at DigitalOcean via Docker drivers and swarm. Our developers as well as our production servers use it as well, being our stack composed of a total of 4 different nodes, a MongoDB container; an elasticsearch container; a nodejs container and our discovery service container, comprising Consul key-value database to store all data from our slave nodes. It's solely maintained by our development team, but the system built within is widely used by our staff as well as the company's clients, spread throughout the world.
- Its topology isolation is in my opinion an unbeatable feature. In our systems we have the need of parallel Java 7 and 8 versions to be running together. Without Docker that would not have been made possible.
- Docker Swarm, taking care of our load-balance characteristics so needed for our systems is a must have.
- Docker composer is a very powerful feature, therein I can have my containers scripted and each of its continuous integration and deployment separated with each of its own concerns isolated whilst all being nicely bootstrapped together under the same "docker-compose up" command.
- Some commands are not very intuitive. In order to have an entire swarm properly functioning [specifically for the scenario we have at our company] wasn't a simple task, having to maintain a very wide range of environment variables safely and nicely kept and good for use. The pipeline to have such a topology ready wasn't simple to figure out how to come up with.
- Some volumes, if not properly shut down when its necessary, will take up to all your disk space. The extra -v attribute wasn't too obvious to use when removing an specific volume leading us to a huge headache.
- Some containers, though exposed as official ones at docker.hub.com, are very space and memory consuming. We have do figure out our own containers for pretty much everything, even though the services that were necessary in the containers were pretty vanilla.
March 18, 2016
Docker in play
Its simple and easy to build and run containers on bare metal VMs without much sys admin experience.
- Developers are able to set up workstation in their local in couple of secs.
- docker image pull is taking more time.
- Containers are crashing some times due to teh file system or daemon issue.
March 14, 2016
Docker Rocker
We use docker in our CI builds from creating a custom Linux image to deploying our latest code from docker registry
- Simplicity/ Efficiency
- Isolation/ Separation of Concerns
- Works well with cloud deployments using services like AWS
- Supports build automation with docker registry
- I understand docker is evolving very well, however wish there were more logging support
- A Docker dashboard that gives insights and statistics
March 14, 2016
Docker for the masses!
We are using Docker to run our microservices across our clusters. Docker gives us the ability to run containers in a centrally packaged and non-dependency hell stricken environment. We use apache mesos w/ marathon as our orchestrator of choice with gluster providing the distributed filesystem back end. It just works.
- Application Portability
- Scaling
- Reduces Dependency Hell
- Security
March 11, 2016
Docker...a huge win!
We are using Docker to deploy multiple services for our company.
Docker allows us to deploy more stable apps, since containers provide an identical application-environment across multiple deployment-environments.
Docker also allows us to differentiate between server/compute infrastructure and application infrastructure.
Ops manages the cluster of servers, while application developers simply run containers on the cluster.
Docker allows us to deploy more stable apps, since containers provide an identical application-environment across multiple deployment-environments.
Docker also allows us to differentiate between server/compute infrastructure and application infrastructure.
Ops manages the cluster of servers, while application developers simply run containers on the cluster.
- Application Runtime Provisioning: Instead of requiring a devops engineer to craft a lengthy provisioning configuration for an application, Devs can easily create a Dockerfile that builds the exact runtime needed for their applications
- Polygot environments: Now that services are are individually provisioned for their task (as opposed to servers provisioned for their task) polyglot services are much more simple. Using the best-tool-for-the-job is simple
- Scaling is easy: Need to scale a service from 5 to 15 nodes? Simply run 10 more containers across the server cluster. Startup is near instant for containers.
- Application Architecture has Improved: Before Docker, our team was nowhere close to 12-factor applications. Docker has allowed us to still manage our own infrastructure, yet we're now building highly-scalable 12-factor apps.
- Service registration and discovery could easily be implemented into Docker/Swarm and would make new-infrastructure startup much simpler.
March 09, 2016
Docker for research reproducibility
As a research organization, we utilize and develop bioinformatics tools as our contribution to the research communities. In particular, we address the research reproducibility issues by developing Docker containers to wrap our research pipelines. Currently we use GitHub and DockerHub as a public repository for other users. Since the users are targeted for a wide range of users (not necessarily tech savvy), graphical user interface is essential. One of the challenges that Docker users currently face is to deliver the graphical user interface from Docker to the user.
- Light weight and portable.
- Easy to share (either by Docker file or as a container/DockerHub).
- Same environment regardless of users operating system.
- Docker is mainly a command line tool; delivering a graphical users interface out of a container is still a problem.
- When Docker runs within a VM as in the case of Mac and Windows users, transferring files in and out of Docker is challenging.
- Since with Mac and Windows users Docker runs within a VM, there's an extensive overhead that need careful consideration.