Mirantis Container Cloud Reviews

The primary use case is for enhancing security by integrating the tool for security identity and compliance, creating a secure container environment. This helps to manage services running within the pod, reducing operational overhead. 

The solution avoids setting up and managing processes manually, focusing on cost efficiency, as users pay only for the nodes in use with auto-scaling capabilities. Mirantis Container Cloud supports Azure and AWS Kubernetes services.

The solution has enhanced the security and compliance management of container environments which reduces operational overhead and costs. 

With the auto-scaling capability, the cost is optimized since we only pay for the nodes currently in use. It has also contributed to reducing security risks through features like real-time vulnerability scanning and improved identity and access management integration. 

It allows the development and IT teams to focus on building applications rather than managing infrastructure.

Mirantis Container Cloud provides significant features such as real-time vulnerability scanning and patching for container images and Kubernetes components, reducing security risks. 

Its integration with identity providers like LDAP and Okta ensures secure user access to container resources. It includes an observability and monitoring solution through Grafana and Datadog which, even though it can be improved, still provides insights into cloud performance. 

It simplifies deployment through managed Kubernetes services and allows for a streamlined command-line setup.

Mirantis Container Cloud could improve in simplifying security and compliance management, particularly in vulnerability scanning and patching. Enhancing RBAC integration with identity providers like LDAP and Okta would secure access to container resources better. 

Streamlining container monitoring, which is currently complex to set up, and providing advanced analytics for predicting potential issues before impacting the production environment could also be beneficial. 

User experience can be improved by simplifying the setup and configuration process to reduce operational overhead.

I have been working with Mirantis Container Cloud solutions for over seven years.

The scalability is very efficient due to the auto-scaling capability of the nodes.

I have not directly contacted Mirantis' technical support. Our inquiries are mostly handled through Azure or AWS support.

Positive

Previously, we have used Docker Swarm which has integrated well with Mirantis Container Cloud due to their acquisition of Docker's enterprise solution.

The initial setup can take four to five hours, but using managed services like those from AKA simplifies the process considerably. With configuration files and automation tools like Terraform, the setup becomes straightforward and time-efficient.

We have our own technical support team who coordinate with AWS or Azure if further assistance is required.

The cost savings are significant as you only pay for the active nodes. Managed Kubernetes services ensure cost optimization with their auto-scaling capabilities.

We have evaluated solutions from Red Hat's OpenShift for container management, which provides a user-friendly, UI-based management platform.

I'd rate the solution eight out of ten.

We are worldwide distributors of Mirantis. There are many use cases. One of the use cases is for the container cloud, and the other use case is for your run time. They have a solution for container run time. 

When you have Kubernetes, you can use Mirantis Container Cloud to manage your Kubernetes for easy access and security. It also helps you to manage your CI/CD system. It helps you to build a container-oriented developer workflow. So, if you're building an application in Kubernetes, it provides you with a Kubernetes engine. They also have a product called Mirantis OpenStack. OpenStack is a platform where you can manage your cloud environment.

Mirantis Kubernetes Engine is very valuable. You can build and run your applications with Mirantis Kubernetes Engine. The next best thing they have is Mirantis OpenStack. It's a Mirantis product. It's an open-source cloud computing platform. It's mostly deployed as infrastructure-as-a-service in both public and private clouds where you can run not just continuous but also your virtual servers. So, any of the resources can be made available to the users.

Its integration capability is amazing. One thing about every single solution or product in the containerization or DevOps world is that it helps to integrate really well because we are not talking about one use case here. We are talking about multiple use cases. When it comes to the integration part, it's the basic functionality, but for any product, at the end of the day, security is extremely relevant. I personally feel like you have to constantly strive towards being more secure. You can never be 100% secure, and you have to work more toward security. It's as simple as that. That's where every product has room to improve. Whether it's Mirantis, Docker, or even the other vendor that we work with called Sysdig, all of these organizations always strive to be extremely secure, and that is something that they are working towards every day. That's because the kind of problems that are being faced today will not be similar to what comes tomorrow. There will be a hundred new threats. It's an ongoing journey when it comes to security.

I've been using this solution for a few years. Mirantis Container Cloud used to be one of the Docker solutions before. It was formerly known as Docker Enterprise. It was acquired by Mirantis, and now it is called Mirantis Container Cloud.

Its stability is amazing. It's perfect. I'd rate it a 10 out of 10 in terms of stability.

Its scalability is amazing. Scalability is one of the major use cases why people go for Mirantis. You can go from 1 to 100 in no time. It can be automated. With the kind of platform it is, it would make life so much easier for any organization. If you look at e-commerce companies, the workload is different every day. On Black Friday, you have three to four times more traffic than normal. In such cases, to scale, you need to have these kinds of tools so that scalability is seamless.

We have a lot of customers. If you look at the Fortune 500 companies, 60% to 70% of them are already using OpenStack.

Their technical support is amazing. Mirantis provides two types of technical support. It's a part of your license. If you are purchasing a license for your lab environment where the developers are building applications and the customers aren't using it, you can always go for 8x5 support where Mirantis provides technical support on all working days.

If you want your license to run the actual workload or live application that customers are using, there is 24x7 support because you don't want any delays. When you look at most of the applications in e-commerce, they are basically the gateway. They are generating money, and you don't want any delays. In that case, Mirantis can provide 24x7 support.

It's a great solution. It's a great competition to OpenShift. OpenShift has a huge market because they marketed it very well, but Mirantis Container Cloud is as good as any other container cloud solution. It's a containerization platform at an enterprise level. Docker is more at the desktop level, where you just run new containers on your desktop, but when it comes to scanning a huge application in a production environment, Mirantis works very well. It's a solution for your servers.

It's straightforward, but there is a certain level of complexity when you're deploying anything on a server level. That is applicable to all containerization platforms such as OpenShift or Tanzu, but you get great support from Mirantis for setting up everything.

It can be done within three working days. The deployment process is pretty basic. Before deployment, we need to have a complete idea of the infrastructure and the customer's needs. We need to know the kind of infrastructure they have and the workload that they would be running. Based on that, we do the sizing and deployment.

It can be deployed by one or two engineers. Even one engineer can get it done. Its deployment is straightforward.

Its licensing is on a yearly basis. 

People have heard about OpenShift a lot. People have heard about Tanzu a lot, but these solutions are too expensive. Mirantis does the same job, and it has a history of being a part of Docker. I don't think anyone can do containers better than Docker. Therefore, you should totally consider Mirantis. You don't even have to pay that much.

We have to do a lot of marketing for Mirantis because certain customers had not even heard about Mirantis. There's a huge gap in the market. We are trying to create more awareness, but it's a great solution. It is as good as any other containerized platform. So, I'd definitely recommend trying it out.

The most important feature that I would focus on is Mirantis OpenStack. OpenStack is an open-source platform, but Mirantis has an enterprise version for it.

In terms of the use case and what it provides, when you compare it with the rest of the solutions in the market, it's a 10 out of 10. OpenShift does a great job; Tanzu does a great job; and Rancher does a great job. Mirantis is as good as any other product. Like any other product, they have to keep on working on security. It's an ongoing journey. 

We use the solution for containerization and link Kubernetes to the Container.

The solution is simple and faster.

The solution is easy to use and difficult to understand. There are many courses available since it is difficult and has many things. Only experts can use it.

I have been using Mirantis Container Cloud for six months.

There were no issues with the solution.

I rate the solution’s stability a nine out of ten.

We use the application to monitor and orchestrate any applications and workloads.

I rate the solution’s scalability a ten out of ten.

Overall, I rate the solution a nine out of ten.

Using Docker for most of the environments that I worked for. As an expert, I am working on different environments each time depending on the customer requirements. Development, staging, pre-production and production, each one of them having at least 25 servers implemented on different solutions sometimes like VMware, AWS, Azure and Oracle Cloud. 

Docker allows me to automate everything for these environments which saves a lot of time to sync the environment with each other and keep them up to date anytime. 

By using Docker and introducing this tool to different organizations, it provides repeatable development, build, test, and production environments, and allows every team member to work in a production parity environment, include to that, app isolation, simplicity, and faster configurations. And the most important benefits for most organizations is continuous deployment and testing.

Different features, but the most valuable is Docker images that allows you to build your own image and upload it to a repository, and use it again anytime. 

Another feature which is Docker scaling using a docker-compose file: It's very simple and easy to use in preventing any human interaction.

The last one is Docker Swarm that manages a cluster of Docker Engines.

• I would love to see if more supported applications could be used under Docker.
• Improving scalability, technical debt, and making it easier to troubleshoot and monitor.
• One last thing which is the performance tuning issue.

Using this solution for a production environment that should be working 24/7 is the biggest proof of stability.

Very easy to use, all you need to have is the basic knowledge with Docker Compose.

Since I've begun using Docker EE, I have full access to Docker's enterprise technical support team. I can manage cases, and view entitlements using the Docker support site.

I started using Docker more than five years ago and before that, LXC (Linux Containers), also Google Kubernetes as I mentioned before. It all depends on the customer requirement and what they want from the application, and which features they will use. 

Depends on the environment and what you need to use. Most of the features have full online documentation with live examples.

We are the vendor, so technically we are providing the solution for the client each time: different client, different requirements and different infrastructure. 

You will notice a big difference for sure. Also, the below link will allow you to calculate the ROI.

https://www.docker.com/roicalc....

For the features and benefits of using Docker, the price is very reasonable, but the licensing is not easy. But to be honest this is a very promising technology, include to that a very fast growing technology. So within the next five years, the licensing will not be an issue. 

Google Kubernetes.

I recommended the tech guys that haven't used it so far, or if their company is still using the transitional infrastructure, they should give it a try. 

I'm working for cybersecurity, so there are some thread data pipelines where we have data processing and then the pipelines are built and being containerized and then exported to the pipelines.

We're using version 20.10.11. It's deployed on a private cloud.

There are more than 20 people using this solution in my organization. We are all data engineers, and our managers are also from the same background. There are also machine learning engineers using this solution.

Before using this solution, we didn't have any kind of platform. This solution allows us to run anything and then post it like a single file. 

The solution as a whole serves a very good purpose.

The UI is very useful. We can look at all the remote repositories of the images and the volumes and containers. It shows all the images along with the total size. There is a huge difference by looking into the terminal and the UI.

An improvement would be automated testing.

I've been using this solution for three months.

The stability is good. We had a few issues before in terms of just running an application and explaining to the other teams and stuff. Because of this application, it's easier for the DevOps engineer. 

We don't need to dig around to know what is happening. We just run the container and put it in the pipeline and then it runs.

We haven't raised any tickets yet. We have a particular infrastructure team, and that team helps us.

It's pretty straightforward. It was easy to install on Windows rather than on a MacBook. On the MacBook, it was a little difficult, probably because of the version that my company is using. We had a little bit of confusion with that.

Everything was done onsite.

I would rate setup 4 out of 5.

I would rate this solution 9 out of 10.

It's a very good application. You don't need to do anything. Just deploy it, run it, and then it does all the work by itself. It's a piece of cake for someone new. If I'm a DevOps engineer, I don't need to worry about anything. I just have to run a command and it shows the errors. Then, I pass it to the other team and they look into it.

It's easy and straightforward to do the deployments. Before, we had to do the manual container when it comes to deployment. Now, you just make an image and then run it by using the commands.

We use Mirantis for nearly everything, starting with development. The developers use Mirantis to basically package the application. We use Kubernetes, and both Mirantis and Kubernetes are used locally by developers. The container runtime is done by Mirantis.

We use Mirantis for our CICD pipelines as well. For very runner in GitLab, a Mirantis container is spawned and then an application is built and some tests are run, and all of that is done in Mirantis containers.

The same goes for production. An image is promoted and tagged and published to a Mirantis registry, and then later pulled in by another agent that's running in Kubernetes.

Did not use Mirantis Container Cloud in the organization.

I think the volume binding is a really interesting feature. For example, if you're running a Mirantis container on your host machine, you can bind a directory of files by the container and use the overlay file system. 

Swarm is quite okay for smaller cases. You don't need Kubernetes and all the other orchestration tools for everything. It works for that use case pretty well.

I think the build time can be better. There's a lot of work done by Mirantis for BuildKit, for example, or Buildx, and I think there is a lot of stuff that can be done over there. 

Some improvements can be made on the Docker Compose level with some dependencies. For example, if you have a service that's dependent on another service, you can't do that today with Docker Compose.

Also, if Mirantis can leverage open source Kubernetes as part of its own offering, I think it would be a huge hit because every developer uses Mirantis. People know Containers because of Docker, and I feel that if they collaborate or incorporate Kubernetes into the Mirantis runtime it would be a big thing because everybody needs local environments and everybody needs to assemble environments for testing, A/B deployments, or production, and have as much of a reproducible environment as possible. I think that would be a huge success.

I would love to see the QUIC protocol support apart from TCP and UDP in Mirantis. I think that they would be the first one to do it because it's not really there at the moment with any other container runtimes that I know of.

I have been using this solution for about six years now. 

I think it's really stable. There were problems in the past, like you have with every software, but I think it's pretty stable now. I have seen very few crashes of the Docker daemon itself, but I'm not talking about the containers because that's not Docker' s job. The stability of those depends what you have learning in your container. As far as the runtime is concerned, I think it's decently stable.

The solution is definitely scalable, but only to some degree. For example, Mirantis did make an effort to get into the orchestration world by having Docker Swarm, but I don't think a lot of people use it because of the other orchestration tools available. I think that's where the scalability problem comes in.

But now with the Mirantis runtime being removed from Kubernetes, which is the industry-wide standard for orchestration of containers, I think it's going in a direction that is not super scalable. Also, with the recent licensing changing with Docker Desktop, a lot of companies are opting to stop using that and switching to another solution like Rancher Desktop, which gives you a UI. If you want to use Docker Desktop in a commercial environment, you have to pay a per user fee. It might be okay for conglomerates and enterprises, but it's not okay for midsize or small companies, because they're tight on budget.

I think there are some scalability issues from my point of view, from the business model and the tech model, and I think stepping out of Kubernetes is a huge setback.

There are currently 200+ people using this solution in my company. 

I have never had to use tech support because I use the documentation, which is pretty decent from my point of view. Also, the community is huge, so there's QAs and forums and discussions going on.

I don't think there's strong reasoning behind why my company decided to go with Mirantis because it used to be, and still is to some degree, the standard for containers. When it comes to containers, what comes to your mind is basically Docker. 

In my organization, we have a lot of developers that are developing applications on top of Kubernetes. Just to keep in sync with the newer version, they decided to switch from Mirantis to Containerd to run their containers, so I think it's changing. In my company, a lot of people are not even using Docker Desktop. Some people are using it because they're used to it and the company had a license for them, but a lot of people switched to an open source alternative to have some DUI for managing their containers.

The initial setup is pretty easy. I think it's super easy with the universal builds offered by Docker for ARM64, Linux, Windows, etc. Even for people who are not familiar with terminal and text files, you can use the Docker Desktop UI to manage all your running containers, images, and modify your Docker daemon JSON file. I think it's really easy as a starting point.

With open source, you can use Mirantis completely free. If you're using Docker Desktop in a commercial environment, you do have to pay a fee, but if you're using the Mirantis runtime, just the daemon and the runtime, you don't have to pay anything. It's all open source. The code is there for BuildKit on GitHub. There's a community, the MOBI project, and you don't have to pay anything.

If you were to use Mirantis for the first time, I would really advise you just to look into the basics of understanding containers in general, anc realize that Mirantis is an abstraction or a way or runtime to run your containers. It is an industry-wide standard now, when it comes to distributing the images, but that's also shifting now to OCI images. I would advise looking into other container runtimes as well, and keep your vision broad and try to make conscious decisions rather than being biased and just following the herd.

I would rate this solution as a seven out of ten because it has really educated users. It created a lot of shift in the industry for using containers. I feel it's stable because it hasn't crashed very much in my experience. The reason I gave this a little bit of a lower number while saying good things about it, is because I don't like how the community' is responding nowadays, especially collaborating with other bigger communities. One of the examples is Kubernetes, for example. There was a backlash and they couldn't agree to stuff. It's really a big thing at the moment, and it will be for the next couple of years.

I use the solution in my company since we have some in-house applications, and to spin up those applications, we use Docker Enterprise.

The most valuable features of the solution are its fairly good UI design and its ability to let users view logs.

Though I am unsure, I feel that the product lacks to offer a proper health status of the images which are running, making it an area where improvements are required.

I have been using Mirantis Container Cloud for six months. I work with the tool's desktop version. I am just a user of the tool.

Stability-wise, I rate the solution a ten out of ten.

Scalability-wise, I rate the solution a ten out of ten.

Around 20 people in my company use the product.

The solution offers a good online community that offers users the option to ask questions related to the product and get answers to troubleshoot the issues.

The product's initial setup phase is simple.

The solution is deployed on an on-premises model.

I rate the product price an eight on a scale of one to ten, where one means low price and ten means high price.

Maybe the other people in my company's environment might be using Doctor Enterprise to manage multi-cloud Kubernetes environments, but I don't use it for that.

The product optimizes and makes DevOps workflow better since it spins up images very fast, and it is a good thing that I have seen in the tool. It is easy to manage which Docker needs to be run and which one needs to be stopped, and it is an area where I use the product the most.

I don't use the tool's centralized management console. I use it individually.

I use the single dashboard option provided by the tool, and if I need to be helpful.

I recommend the product to those who plan to use it.

I rate the tool a ten out of ten.

The solution containerizes software. 

Mirantis Container Cloud needs to improve its documentation. 

I have been using the solution for half a year. 

I rate the solution's stability an eight out of ten. 

I rate Mirantis Container Cloud's scalability a ten on ten. I am the only one using it. 

Mirantis Container Cloud's installation is straightforward and is completed in half an hour. 

Mirantis Container Cloud is free. However, there are features for which you need to pay. 

I rate the solution an eight out of ten.