Mirantis Container Cloud should have AI integration tools, which are not available right now. These tools should assist in app scalability and deployment error handling.
Docker is a time-tested, proven solution with industry-wide applications. There can be challenges with port mapping, however, that's not related to Docker itself.
The learning curve with Docker is huge and extensive. Adopting Docker is a bit difficult because it requires a lot of expertise and background, including an understanding of networking and security concepts. Many professionals are facing issues with the different architectures that interact with each other in Docker. Whenever in our company, we are working with the production environment, professionals are hesitant to adopt Docker due to the extensive learning curve, and most of the team members in our company are more accustomed to an environment like VMware instead of Docker. Docker runs on scripts, so if AI can automate most of the scripting process in Docker, it would be a great advantage in the future version of Docker. As of now, we can create scripts utilizing most of the functions within Docker, but that initial planning phase wherein to understand exactly how you will plan for the resources, how you will convert applications into a Docker-based image, and similar tasks needs to be simplified so that more professionals can adopt Docker.
Sometimes, we have sync-up issues where the build doesn't get processed due to these sync issues, causing the build to fail. That's one of the drawbacks I see. When we did a huge sync-up, we faced a couple of issues. It takes some time for us to complete the sync-up. For frequent, smaller updates, we haven't had any issues. However, challenges can arise for those who prefer doing everything in one go. This might not necessarily be due to the tool itself but because of the approach of doing everything in a single batch.
The vendor should release a monitoring tool or include monitoring capabilities in Docker that can be used to monitor container performance and other Docker-based solutions.
Docker volumes. When I integrated volumes, I faced challenges. I have not essentially used add volumes to the existing instances. Maybe, I am not familiar with adding volumes to the existing Docker images. That might be a challenge, but it should be fairly straightforward. I'm just not aware of it. So just for me personally, it is a challenge. Docker has all the major support already. They should publish all the build images of Docker on an open-source resource like Github. They should support all the stuff. For example, now Docker supplies all these standard images, like database images or whatever image that the standard application is related to. Whenever there is Docker Compose information available on an open-source community project, that image should also be maintained and supported by Docker itself instead of the dev team doing it. Docker should take an interest in building those images and maintaining them for the public community projects that are hosted.
I'd like to see the new update on containers and what you can achieve with the new version of Docker by using containers. I would also like to know the range of applications for which it can be used. I want to see if new architectures have been incorporated in Docker or if we have to wait for another release.
I have encountered network issues while connecting with microservices. I want to optimize the application layers over the bucket. It should also have better documentation.
Senior Technical Lead at a consultancy with 10,001+ employees
Real User
May 1, 2023
The product does not have an extensive documentation. The tool does not have good scenarios. We have to go through the GitHub repository and investigate similar scenarios. Also, if you are copying multiple things, then you can jeopardize the copy number. The copying aspect also lacks a UI part. We also need to limit the memory.
I'm not a developer but a salesperson, so I cannot contribute much in terms of what needs improvement in the solution from a technical perspective. From a marketing perspective, we, as distributors, wish that Docker would figure out a way to reach more customers. Marketing of Docker is one area that needs to improve. So, since Docker was commercialized a year and a half ago, it should plan to work on its marketing part. Also, there is room for improvement in terms of the security provided by the solution. So, it should be an ongoing process that never ends.
Solutions Architect at a tech services company with 51-200 employees
Real User
Mar 9, 2023
We have found that it is not easy to install it into a Windows system. I get very frustrated with Windows. When I install a Docker instance on a Windows machine, it is not easy to handle. In contrast, it's very easy to use on the Mac OS. I'd like the solution to be more flexible.
There may not be much room for improvement with Docker as it has greatly evolved. However, one area that could be improved upon is the documentation on their website which was once easy to follow but has become quite terrible with numerous versions being released. As an example, the installation process for Docker now requires more than just a one-line command, causing inconvenience. Additionally, based on my experience as a college instructor, teaching students to install Docker was a difficult task due to the lack of straightforward and easy-to-follow documentation. Docker should focus on improving their documentation to make it more user-friendly for all. In an upcoming release of the solution, the UI should be made even more user-friendly and comprehensive, as it currently requires a multi-step process to set up a registry or host a container. A one-click solution that streamlines the entire process and makes storing, leaving, and cleaning up images significantly easier. This feature would greatly benefit those who have previously struggled with additional cleaning when hosting their own container, and it would make the end-to-end Docker experience more accessible and efficient.
I would like to see a more UI-based tool so that students can easily understand it rather than memorizing all of the Docker commands. Some people try using Docker desktop and containers to make it graphical. Docker Swarm could have more advanced features, like Kubernetes, which has an auto scaling feature and cell-filling capabilities.
We have encountered a few performance issues with docker along the way, but this does not happen often. Nevertheless, I would like Docker's performance to be better. Docker has less support if you use a container. However, with Linux, I need to use a container. I would love to have it available on Linux.
Cloud Operations Center Analyst at a pharma/biotech company with 10,001+ employees
Real User
Oct 4, 2022
We would like to see improvement in adding the node into the Docker Swarm cluster, as at present it is a little tricky and requires a lot of manual steps.
Unix/Linux Systems Administrator at a financial services firm with 10,001+ employees
Real User
Aug 19, 2022
If you install Docker on a host, it creates its own firewalls. It can become an issue. Usually, when you want to install Docker, you need to restart the firewall or restart the active tables on the machine, but this is not the case with Kubernetes. It uses the default set up by the next administrator, but with Docker, you have to restart the firewall and restart Docker before the firewall on the system will be okay. If you do not the rules will not be created.
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.
Transformation Leader at TEKsystems (ex Aston Carter)
Real User
May 30, 2019
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.
Cloud sales & support for rackspace with 11-50 employees
Real User
Dec 19, 2018
Sometimes the basic support is a bit difficult if you have a firewall and cloud servers behind the firewall and then try to implement the backup solution, it can be a bit difficult to do by yourself. If you have a Rackspace engineer, it is easier, because they know the procedures, but that service is not cheap. It can be an extra $500 for that extra service, per month. It would be nice to see that cost decrease.
* 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.
Mirantis Container Cloud should have AI integration tools, which are not available right now. These tools should assist in app scalability and deployment error handling.
In terms of communication between services, perhaps the configuration within networks between containers could be improved.
Docker is a time-tested, proven solution with industry-wide applications. There can be challenges with port mapping, however, that's not related to Docker itself.
Enhancing artificial intelligence capabilities and cluster management should be a priority. It should facilitate some security management.
The stability could be improved.
Docker needs to improve its pricing.
The solution could offer better documentation.
The learning curve with Docker is huge and extensive. Adopting Docker is a bit difficult because it requires a lot of expertise and background, including an understanding of networking and security concepts. Many professionals are facing issues with the different architectures that interact with each other in Docker. Whenever in our company, we are working with the production environment, professionals are hesitant to adopt Docker due to the extensive learning curve, and most of the team members in our company are more accustomed to an environment like VMware instead of Docker. Docker runs on scripts, so if AI can automate most of the scripting process in Docker, it would be a great advantage in the future version of Docker. As of now, we can create scripts utilizing most of the functions within Docker, but that initial planning phase wherein to understand exactly how you will plan for the resources, how you will convert applications into a Docker-based image, and similar tasks needs to be simplified so that more professionals can adopt Docker.
Sometimes, we have sync-up issues where the build doesn't get processed due to these sync issues, causing the build to fail. That's one of the drawbacks I see. When we did a huge sync-up, we faced a couple of issues. It takes some time for us to complete the sync-up. For frequent, smaller updates, we haven't had any issues. However, challenges can arise for those who prefer doing everything in one go. This might not necessarily be due to the tool itself but because of the approach of doing everything in a single batch.
There's always room for improvement. Sometimes there's a bug or defect in the solution. However, the Docker team works on fixing it.
The vendor should release a monitoring tool or include monitoring capabilities in Docker that can be used to monitor container performance and other Docker-based solutions.
Docker management is very difficult when we have a large number of nodes.
Sometimes, it can become heavy and cause performance issues.
Docker volumes. When I integrated volumes, I faced challenges. I have not essentially used add volumes to the existing instances. Maybe, I am not familiar with adding volumes to the existing Docker images. That might be a challenge, but it should be fairly straightforward. I'm just not aware of it. So just for me personally, it is a challenge. Docker has all the major support already. They should publish all the build images of Docker on an open-source resource like Github. They should support all the stuff. For example, now Docker supplies all these standard images, like database images or whatever image that the standard application is related to. Whenever there is Docker Compose information available on an open-source community project, that image should also be maintained and supported by Docker itself instead of the dev team doing it. Docker should take an interest in building those images and maintaining them for the public community projects that are hosted.
We are facing multiple issues with the solution's stability.
I'd like to see the new update on containers and what you can achieve with the new version of Docker by using containers. I would also like to know the range of applications for which it can be used. I want to see if new architectures have been incorporated in Docker or if we have to wait for another release.
I have encountered network issues while connecting with microservices. I want to optimize the application layers over the bucket. It should also have better documentation.
Stability is an area with a shortcoming. Hence, stability needs to be improved.
The product does not have an extensive documentation. The tool does not have good scenarios. We have to go through the GitHub repository and investigate similar scenarios. Also, if you are copying multiple things, then you can jeopardize the copy number. The copying aspect also lacks a UI part. We also need to limit the memory.
I'm not a developer but a salesperson, so I cannot contribute much in terms of what needs improvement in the solution from a technical perspective. From a marketing perspective, we, as distributors, wish that Docker would figure out a way to reach more customers. Marketing of Docker is one area that needs to improve. So, since Docker was commercialized a year and a half ago, it should plan to work on its marketing part. Also, there is room for improvement in terms of the security provided by the solution. So, it should be an ongoing process that never ends.
We have found that it is not easy to install it into a Windows system. I get very frustrated with Windows. When I install a Docker instance on a Windows machine, it is not easy to handle. In contrast, it's very easy to use on the Mac OS. I'd like the solution to be more flexible.
There may not be much room for improvement with Docker as it has greatly evolved. However, one area that could be improved upon is the documentation on their website which was once easy to follow but has become quite terrible with numerous versions being released. As an example, the installation process for Docker now requires more than just a one-line command, causing inconvenience. Additionally, based on my experience as a college instructor, teaching students to install Docker was a difficult task due to the lack of straightforward and easy-to-follow documentation. Docker should focus on improving their documentation to make it more user-friendly for all. In an upcoming release of the solution, the UI should be made even more user-friendly and comprehensive, as it currently requires a multi-step process to set up a registry or host a container. A one-click solution that streamlines the entire process and makes storing, leaving, and cleaning up images significantly easier. This feature would greatly benefit those who have previously struggled with additional cleaning when hosting their own container, and it would make the end-to-end Docker experience more accessible and efficient.
I would like to see a more UI-based tool so that students can easily understand it rather than memorizing all of the Docker commands. Some people try using Docker desktop and containers to make it graphical. Docker Swarm could have more advanced features, like Kubernetes, which has an auto scaling feature and cell-filling capabilities.
We have encountered a few performance issues with docker along the way, but this does not happen often. Nevertheless, I would like Docker's performance to be better. Docker has less support if you use a container. However, with Linux, I need to use a container. I would love to have it available on Linux.
The command line interface could be more intuitive. I constantly struggle with it.
Deployment could be quicker and customer service and support can be improved.
One item that could be improved is the overall stability of Docker.
We would like to see improvement in adding the node into the Docker Swarm cluster, as at present it is a little tricky and requires a lot of manual steps.
Docker could improve by having security vulnerability reports.
If you install Docker on a host, it creates its own firewalls. It can become an issue. Usually, when you want to install Docker, you need to restart the firewall or restart the active tables on the machine, but this is not the case with Kubernetes. It uses the default set up by the next administrator, but with Docker, you have to restart the firewall and restart Docker before the firewall on the system will be okay. If you do not the rules will not be created.
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.
I think this solution needs better security due to rising threats from the outside world.
Sometimes the basic support is a bit difficult if you have a firewall and cloud servers behind the firewall and then try to implement the backup solution, it can be a bit difficult to do by yourself. If you have a Rackspace engineer, it is easier, because they know the procedures, but that service is not cheap. It can be an extra $500 for that extra service, per month. It would be nice to see that cost decrease.
* 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.