Canonical LXD vs. Mirantis Kubernetes Engine

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Canonical LXD
Score 9.0 out of 10
N/A
Canonical LXD is a Linux container hypervisor.N/A
Mirantis Kubernetes Engine
Score 8.0 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
Canonical LXDMirantis Kubernetes Engine
Editions & Modules
No answers on this topic
Free
$0.00
per year
Basic
$500.00
per year
Offerings
Pricing Offerings
Canonical LXDMirantis Kubernetes Engine
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional DetailsThese 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
Canonical LXDMirantis Kubernetes Engine
Considered Both Products
Canonical LXD

No answer on this topic

Mirantis Kubernetes Engine
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
Docker isn’t a buzz word. It has promising return on investment and a bright future ahead backed up by the open source community.
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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.
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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.
Chose Mirantis Kubernetes Engine
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, …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Chose Mirantis Kubernetes Engine
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 …
Best Alternatives
Canonical LXDMirantis Kubernetes Engine
Small Businesses
Portainer
Portainer
Score 9.0 out of 10
Portainer
Portainer
Score 9.0 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Canonical LXDMirantis Kubernetes Engine
Likelihood to Recommend
-
(0 ratings)
8.3
(0 ratings)
Likelihood to Renew
-
(0 ratings)
9.1
(0 ratings)
Usability
-
(0 ratings)
8.0
(0 ratings)
Support Rating
-
(0 ratings)
7.8
(0 ratings)
User Testimonials
Canonical LXDMirantis Kubernetes Engine
Likelihood to Recommend
No answers on this topic
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.
Read full review
Pros
No answers on this topic
  • Containerization - allowing multiple micro-services to function together without in-depth orchestration at the VM level.
  • Rapid deployment - a developer with appropriate access can simply push to the correct remote and the deploy happens automatically from there
  • Decouples provisioning from VM administration - allows containers to be deployed (more) regardless of VM set up.
Read full review
Cons
No answers on this topic
  • 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.
Read full review
Usability
No answers on this topic
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.
Read full review
Support Rating
No answers on this topic
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.
Read full review
Alternatives Considered
No answers on this topic
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.
Read full review
Return on Investment
No answers on this topic
  • 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.
Read full review
ScreenShots