What needs improvement with Mirantis Container Cloud?

Some improvements are needed, particularly related to internal network management compared to Kubernetes.

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.

More integrations with other platforms would be beneficial.

The solution's stability could be improved.

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.

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

There could be an automation feature included in the product. It will speed up application processes and will not require scripting codes.

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

Mirantis Container Cloud needs to improve its documentation.

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 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.

An improvement would be automated testing.

Areas for improvement are the privacy of container management and the documentation. In the next release, I would like to see best practices on how to manage distributed containers and networks.

This solution is open-source and they need to focus on improving the Linux Operating Systems' GUI. It does not have a GUI making it not user-friendly. Additionally, the containers need to improve security and compliance.

This product will only be useful if it can successfully run legacy applications in the cloud.

Integration with Windows is something that can be improved.

Sometimes it is difficult to access the quality of information on Docker. I also feel that it is not a 100% secure product and I'd say there is room for improvement in the security area and functionality. I would also like to see more features inside Docker as well as more integration with different solutions.

Dynamic port association on active containers.

The orchestration and tracing should be improved.

It would be very nice to have a GUI that can be used by any administrator, and not just people who have experience with Docker.

You need to be aware of the complete networking aspects of Docker across walled communications. That is something that you can simplify. For a developer, it is easy to understand if you have networking knowledge. If you are just a developer without networking knowledge, it's very difficult to understand how to communicate across walls using containers. Especially if you're in a call data center. That's the one aspect which I find very difficult. I'm a coder. I've wanted to see an easy way to integrate seamlessly with other systems. For example, Jenkins has a Docker plugin. If you were to write an integration, you need to explicitly write code, especially for customizations. It's not easy to integrate unless you are a coder. If Docker can create some kind of workflow in generic fields, i.e. things that we can integrate with other out of the box tools, that would be great. OpenShift is an alternative to Kubernetes. I find Docker easier to use, but I gave it to an inexperienced developer and it took him a lot of time to understand.

The solution would benefit in improvements made to the storage, cleaning up information from the disk, and reading logs.