Mirantis Container Cloud Reviews

Neutral

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.

Mirantis Container Cloud helps to implement an AI-driven data solution. It has a data-driven approach to business deployments.

One of the most valuable feature is its scalability because it is easy to work with. Even though I haven't fully removed it before, it's simple to get started and develop further. It's comparable to working with languages like C++ and Python. Python. It is easy to understand and more user-friendly.

In my previous years, I have brainstormed about the development of Container software. I have recently shifted focus, but the knowledge gained from those were really helpful. In my experience, Containers have their own complexities and to implement them, open source information is crucial. A software with new features would be beneficial. I suggest to implement a flow-based approach for container sequences, similar to Google Cloud's machine learning. The current process of deploying containers involves too many steps, and a more streamlined method would be appreciated. I've even automated deployment using APIs. Overall, simplifying container management and deployment processes would be valuable.

I have been using Mirantis Container Cloud for the past 6-8 months. 

I can give it an 8 out of 10. There were instances in Mirantis Container Cloud where are warnings well in advance, for example, if you needed to add a volume at scale, it was informed. I appreciate this there before any issues occurred.

I would rate it 7 out of 10. 

The setup is easy and simple. 

I would rate it 8 out o 10. 

The solution is used for a restaurant application. We have developed a new innovative restaurant application that handles the restaurant order system via voice. We also use it for charging management software.

The product is easy to use. It is easy to implement and manage. The implementation of security is also easy.

It will be better if the product provides dynamic load-balancing capabilities. It must also provide policy-based management and security features.

I have been using the solution for four years.

The tool is stable.

The tool is scalable. We currently have four customers, each with approximately 20 users. We might need to increase usage in the future.

We have decided to migrate to the Kubernetes environment.

The setup is straightforward. The deployment takes only one day. I need a virtual network or virtual server to deploy the product. I prepare DevOps scripts, implement the Ubuntu operating system, and implement the Docker environment. After that, I implement the software.

The solution is deployed on promises. We are also implementing it in the cloud environment in Microsoft Azure. Azure is expensive, so we will soon migrate to Amazon. The implementation is easy for us because we have a skilled DevOps engineer.

The deployment can be done in-house. However, we will need a consultant when we decide to go into production.

The implementation is easy. The management of the cloud is easy. These are the benefits we receive from the product.

The product is not expensive. I rate the price a two or three out of ten.

We are providing the solution to our customers. The solution is suitable for mid-range products. If we have enterprise solutions, we must choose Kubernetes-based solutions. We provide software as a service. Overall, I rate the product an eight out of ten.

We use Mirantis Container Cloud to manage web applications. 

I use Docker in combination with Kubernetes. Management of software packages is easy. It also can be done fast. Rolling out new software updates is smoother and faster due to Mirantis Container Cloud. 

You need to have system knowledge to deploy the product. It should be improved. 

I have been using the solution for eight to nine years. 

Mirantis Container Cloud is stable. 

The solution is very scalable. My company has 24,000 users. 

I have never had any issues to contact tech support. We fixed issues ourselves. 

Mirantis Container Cloud's deployment takes around two days to complete. 

We did the deployment in-house. 

I rate the product a nine 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. 

I use it to containerize microservices. It's a comprehensive container solution for managing microservices.

It streamlines the operation of our e-commerce systems for major brands, making deployment easy and cost-effective.

It significantly simplifies our deployment and management processes. We've containerized over ten microservices, improving efficiency and deployment speed.

For Kubernetes management, the key thing is managing containers. It reduces errors compared to traditional servers. Since containers are lighter weight, deploying them is faster. Think about it this way - if an image is smaller and lighter, you can install it much quicker. This is especially beneficial when you need to deploy a large number of containers, potentially in just minutes or even seconds.

The multi-cloud support has positively influenced our maintenance and operational efficiency.

More integrations with other platforms would be beneficial.

I have been using it for more than five years. 

It is a stable solution. It is nearly perfect. I would rate the stability a ten out of ten. 

It is a scalable solution. I would rate the scalability a ten out of ten. 

It was extensively used in our company. There were around a thousand end users using it. 

Deployment time varies depending on the cluster configuration. Sometimes, it can take days. It depends on the configuration of the clusters. In some cases, like the configuration assessment can take longer. But that's not because of Docker itself.

It's just because we might not have information about the Docker configuration, for example. Let's say you have a cluster in another Kubernetes environment, and you want to use a port from that other cluster on your current Kubernetes cluster. That can make things more complex.

We used a consultant's help.

I recommend it.

Overall, I would rate the solution a seven out of ten. 

We use Mirantis Container Cloud to package and configure our microservices. Whether it's a simple standalone service or a service with a PostgreSQL or MongoDB connection, we handle it all in a Docker file.

We don't use Mirantis Container Cloud straightforwardly. We use it through GCP and Google's managed Kubernetes environment.

Mirantis Container Cloud operates similarly to how we interact with databases. It provides a comprehensive platform for deploying and managing containerized applications across cloud environments.

The solution makes it easy to reconfigure your microservices. Each microservice has its configuration stored in one file. If you need to scale or perform any other action, you can access these configuration files and scale the specific part of your system. This approach divides the system into manageable pieces while keeping them interconnected. The configurations are centralized, preventing scattered configurations across random places.

The solution's stability could be improved. 

I have been using Mirantis Container Cloud for two years.

Mirantis Container Cloud is designed to facilitate easy setup and reconfiguration of microservices. Each microservice has its configuration stored in a single file. Scaling or adjusting components can be achieved by modifying these Docker files. This approach breaks down the system into manageable pieces while ensuring coherence and centralized configuration management. Overall, it offers stability and ease of management.

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

The solution is scalable.

We have a dedicated team that handles all requests. They can contact support for issues like Postgres or anything else. In the past few years, we've encountered some problems with containers around five times, but our team has managed to address them effectively.

The initial setup is straightforward but requires some knowledge and research to be executed properly. Once you understand the process, it becomes simple, involving configuration in one file. It is easy to reconfigure

Google provides us with GKE, a managed global cloud Kubernetes engine. We've deployed our application there. It's familiar territory for us, and scaling up or down is incredibly simple. Our workflow revolves around GitHub actions and a specific set of configurations. 

You have support for multiple configurations. Let's say you need a service that uses a SQL database; perhaps you require another well-known SQL database. With Mirantis Container Cloud, you can configure all these in one place. Additionally, these services can connect seamlessly. You can specify the ports on which they connect in a single configuration file, consolidating all settings in one central location.

All these cloud platforms—Google, Amazon, Microsoft Azure, and others—offer a managed Docker environment.

We are also using Mirantis Container Cloud for development. It simplifies the setup needed for your project. Instead of installing various components individually on your Windows or IOS, such as a SQL database, a NoSQL database, DocIQ, with Docker, you can install everything within Docker containers. This keeps your project setup separate from your computer's environment. It's really convenient, if you need to transition to a different project with different requirements. You can simply discard the Docker images associated with the previous project and install the new ones for the new project. This process doesn't affect your computer, whether it's running Windows, Mac, Linux, or any other operating system.

It's a great solution. It's designed to handle complex, demanding, and scalable applications. Occasionally, these issues can be challenging to investigate, necessitating support intervention. I recommend this solution.

If you would like to scale your application to get millions of end users. It offers the biggest scalability.

Mirantis is simplifying their setup, stability and the easy use of configuration.

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

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.

We use it as OMS application. It's an Application and Logistics IBM application. That application runs as a container.

I like the deployment automation. I can deploy whenever I want based on the environment, and I can easily roll back to a previous version for testing. Also, the scalability is great. If there's a usage spike, I can easily adjust resources.

There are a couple of things. Firstly, the vaultStore database within Container isn't as efficient as a standalone Container vault. This needs improvement. 

Ideally, Mirantis Container Cloud should seamlessly integrate with traditional software. Right now, incorporating such software into containers feels clunky and disadvantageous. 

We should be able to easily deploy database instances and split traditional software into containerized components for optimal utilization. These advancements would significantly enhance Mirantis Container Cloud's capabilities.

I have experience with this product.

Typically,  stability is fine. Good access.

There are around a thousand end users using this solution. We use it once a week mostly. We have a weekly call to discuss the solution and work on automation for repetitive tasks.

It's hard to find a better container platform. So far, we haven't had any major issues with scalability or anything else.

The customer service and support are good.

Positive

We used Docker. 

The initial setup is easy. I would rate my experience with the initial setup a ten out of ten, with ten being easy to set up. 

The deployment took a couple of hours. We're actually using Azure Cloud for container deployments.

We don't have a private registry. Any images we deploy already exist in our private tenant registry, so pulling them is quick. Mirantis Container has a repository we can enable and install from. So, deployment time really depends on whether the parent image already exists elsewhere.

For all the deployment needs, we didn't need any extra people. The images we create follow strict standards, so maintaining the address center doesn't require much work.

It's not overly expensive. Somewhat okay, maybe slightly below average.

I would suggest others ask about improving the support for database and consider the structure of the applications. Some highly customized applications might require extra effort. 

Overall, I would rate the solution a ten out of ten. It is a good solution.