Docker Enterprise was sold to Mirantis in 2019; that product is now sold as Mirantis Kubernetes Engine. But Docker now offers a 2-product suite that includes Docker Desktop, which they present as a fast way to containerize applications on a desktop; and, Docker Hub, a service for finding and sharing container images with a team and the Docker community, a repository of container images with an array of…
$0
unlimited public repositories
Mirantis Kubernetes Engine
Score 9.4 out of 10
N/A
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.
$0
per year
Pricing
Docker
Mirantis Kubernetes Engine
Editions & Modules
Free
$0
unlimited public repositories
Pro
$5.00
per month per user
Team
$7.00
per month per user
Business
$21
per month per user
Free
$0.00
per year
Basic
$500.00
per year
Offerings
Pricing Offerings
Docker
Mirantis Kubernetes Engine
Free Trial
No
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
These pricing options are compatible with Linux or Windows Server and are per year, per node. The basic version requires maximum online purchase not to exceed 50 nodes. Support/professional services are not included.
More Pricing Information
Community Pulse
Docker
Mirantis Kubernetes Engine
Considered Both Products
Docker
Verified User
Anonymous
Chose Docker
Our team uses Lando which is built on top of Docker. This makes using Docker even easier.
It is easy to use. we can manage multiple images in docker hub. Docker desktop is for accessing images in our desktop. It is very much user friendly as compare to podman.
Docker is by far the industry leader and mainstay when it comes to virtual machines, its really hard to justify using another service like Vagrant. The upcoming monetization of Docker desktop should make things interesting though.
We need a solution where initially we can use an OS to trigger our pipeline to be used by terraform and then later in ansible. After doing all work it automatically get exited and we can reclaim the space of our VM. So we created a gitlab pipeline and at the initial stage we …
The features and capabilities provided by Docker are incomparable and much vast in nature. Docker is much light weight and easy to onboard into the tech stack. It is also well supported by Container orchestration systems like Kubernetes which will be critical when applications …
Did use containerd or LXC for brief evaluation in the past, but settled on Docker and only see Docker as the mainstay for most organizations I worked in, as the container tool of choice so far. Docker is matured, feature-rich, and reliable enough to be the main choice all …
The reason why we are still using Docker right now is due to that is the best among its peers and suits our needs the best. However, the trend we foresee for the future might indicate Amazon lambda could potentially fit our needs to code enviornmentless in the near future.
Docker provides is effective container management and orchestration platform. It is highly suitable for Linux environments and allows the easy and quick deployment of production applications Other alternatives use replication and management of the virtual machines. Docker …
I have used Vagrant for consistent development environments as well. It is a more "heavyweight" solution since it's a complete virtual machine that requires a host like VirtualBox in order to run. With Docker, the container is much more lightweight and just requires the docker …
Prior to docker, we had a custom build and deployment system. For local development, we use VirtualBox to host our VMs, while our custom VMs resided directly on the servers. We chose Docker primarily to allow us to get rid of our custom deployment system, both simplifying build …
While Ansible and Docker focus on solving two different problems, we were previously using Ansible to ensure that all dependencies were automatically setup on new servers and that proper configuration was applied when new nodes were brought up. With docker, most of these …
Vagrant is another software that offers similar [features that] stack to Docker. It offers an isolated container similar to Docker but Docker is lighter weight because it does not have the additional overhead of a VM Container. Docker has a much larger community of developers …
I didn’t select Mirantis Cloud Native Suite (Docker Enterprise) when I joined this organisation it was already being used here. The one thing I can say about Mirantis Cloud Native Suite (Docker Enterprise) is easy to use and creates a good impact in the businesses. So, I …
So far I haven't used any other containerized product except Docker Enterprise because in terms of community support and tutorial videos, Docker has a better reach than other tools. Docker can be easily set up from local to the cloud without worrying about the flavor of OS …
I have not used any other software as a container management solution. Its containerized apps allow the usage of less memory, thus
they start and shut down very fast. This tool is helping the enterprise
software to work quickly against the changing conditions thus offers great
I have heard about others, but all my professional life I have been using Docker as my primary container and the thing is you just don't need anything else right now. Because Kubernetes supports Docker and Docker is open-source and just very simple to get started with. 10 …
Junior Systems Administrator | POS Programming Specialist
Chose Mirantis Kubernetes Engine
FreeNAS, I don't wish to bad mouth any product but it appeared that iXsystems just did not want to help their users or attempt to resolve issues. It looks good on paper and it worked well for me for about 4 years until I needed more support and a more complex and bigger …
Docker has become the defacto service, as far as I have seen, to run Linux or other tools on any OS and architecture and get the same output. I have used vagrant in the past, but it was much more complicated to use. Docker is very common among developers, so documentation and …
Dockers isn't a replacement for VMWare or VirtualBox in all cases. It's fundamentally a different way to solve the development problem. We use Docker when we need a lightweight, fast development scaffold. We use other virtualization solutions if we need GUI access or need a …
I would also compare to BSD Jails, LXC, and Solaris Zones, but they weren't listed. One of the first reasons we decided to use Docker over other container applications is because Docker is the default everyone recommends and is easily the most popular. We found Docker to be …
Docker provides less lock in and more portability than Heroku. You can also easily self host or choose a Docker hosting service. Additionally, there is a wide availability of Docker containers where Heroku build packs are somewhat more limited. Heroku offers a more turnkey …
We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP).
Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being …
Docker is great because of how the Docker Runtime works and how it eliminates the need to have the full operating system overhead that you'd find in a virtual machine (VM), keeping things lightweight and compatible regardless of where you go. Having an isolated, full Linux …
For light weight frontends, the Docker Swarm is the easiest to manage. One person can then mange the production environment and at the same time develop new software.
While we still use virtual machines [for our Docker servers], we prefer Docker containers for our deployments. It really allows for a simpler infrastructure footprint to manage. For example, instead of managing 30 virtual machines with one or two apps on each VM, we could …
I had to use virtual machines before, the last one was VirtualBox. I was only a user there, I wasn't responsible for the configuration, it was a black box for me. When I had to use Docker for the first time I was a skeptic, but it proved to be easy. I can't really compare the …
Doocker lacks a lot of the scaling, automation, integration of 3rd party tools/solutions, and integration of shared high-performance self-healing storage, solutions like Heketi provide those missing pieces.
Docker runs both locally and on the server, whereas VirtualBox is only used locally to create a development environment. Docker gives us the ability to have the exact same environment both in the cloud and on individual developers' laptops. There are no surprises for the team, …
Docker is a different beast in that it is not trying to solve all of your infrastructure problems or most of them, it is simply trying to provide a reliable container serviced based on linux containers in which you can easily and quickly deploy microservices. LXD does provide …
Docker doesn't directly compare to very many other services. It is unique in its field. However, I love how fast Docker services spin up in comparison to VM-based or server-based applications. Docker is being adopted at a fast rate in the industry, so it's great to see Docker …
Before Docker, we were using Chef to manage our deployments. Chef didn't provide the environmental consistency and release confidence we needed. We had a split process between how the build servers, the developers and the deployed environments were managing the software …
You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.
Docker is great for when you would want to use a VM for any given application, but don't need the overhead of the whole OS. Docker containers use very little computing resources, boot up very quickly, and are very easy to set up. An instance where Docker may not be appropriate would be for an application that requires good security. If in this situation, a true VM would probably be your best bet.
Docker has a bit of a learning curve, and it takes some time to become familiar with the tooling and syntax. Transitioning an existing architecture to docker can represent a significant investment.
Docker attempts to provide some level of cross-host container orchestration via swarm, but it falls short of third-party solutions like kubernetes.
We occasionally run into stability issues when the docker daemon is subjected to high load (many applications starting/stopping frequently). In these cases, docker hangs and we have to restart or replace the node.
I have been using Docker for more than 3 years and it really simplifies the modern application development and deployment. I like the ability of Docker to improve efficiency, portability and scalability for developers and operations teams. Another reason for giving this rating is because Docker integrates CI/CD pipelines very well
Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
We need a solution where initially we can use an OS to trigger our pipeline to be used by terraform and then later in ansible. After doing all work it automatically get exited and we can reclaim the space of our VM. So we created a gitlab pipeline and at the initial stage we defined a docker file which will be our base image and we performed all our activities inside that image to build infrastructure using terraform. Integration we have done in our gitlab pipeline and finally we remove the docker image so that the space can be reclaimed immediately.
I have not used any other software as a container management solution. Its containerized apps allow the usage of less memory, thus they start and shut down very fast. This tool is helping the enterprise software to work quickly against the changing conditions thus offers great scaling by simultaneously allowing me to meet the demands, which also leads to easy implementation of the strategies.
It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.
We are able to try things very quickly compared to before. If you need to debug it, changes on X/Y/Z will have an impact on the way your app works, and changing libraries or configurations of the environment easily can improve your development cycles.
In case someone new arrives, the onboarding is pretty easy thanks to Docker. We have tried many configs and images until we reached a point were we have what we want. We don't have to painfully do that again for every new user. We just send him the image.