Docker Reviews

Our primary use is to deploy the applications in a secure environment. We prefer that our developer and the Docker files can make the images. After we have captured the images we use our CI/CD tool and deploy our applications. This makes our publisher fast and our containers are isolated from each other. We increase our security by using Docker. 

The most valuable feature is Docker has a fast learning curve. There are a lot of default options that when you use Docker you do not need to customize or configure it in a way that it slows you down.  The user interface is very nice as well. Docker has good security.

One item that could be improved is the overall stability of Docker.

I have been using Docker for one year.

For the most part, Windows is stable, but sometimes the application crashes and we have to have an error fixed in order for the stability to remain. When it comes to Linux it is not so compatible.

The reason why the company decided to use Docker is that it is easy to learn.

The setup is easy and straightforward.  The Docker site is comprehensive, and you can find all of the documentation, API, details, and comments you need to deploy.

The current cost for us is nothing as an open source.

I would recommend they use the online videos and tutorials and after a week they are going to be ready to start. I would recommend it to anyone to use. I would rate Docker an eight out of ten.

I use Docker for containerization, deployment, and to create packages. Docker has a wide range of uses and integrates well with other command-line tools like Terraform. Docker is most helpful when trying to work with CI/CD pipelines.

Docker's containerization property is its main selling point.

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 been using Docker for one year.

I rate Docker a nine out of ten for stability.

Docker is a very scalable solution. I rate Docker a nine out of ten for scalability.

Docker's initial setup is straightforward. As a command line tool, it also provides you with docks to reference if you get stuck or have issues.

The solution's deployment time depends on your internet latency or internet speed and the size of the container. If you are deploying a very large application, it will take some time to set up.

Docker is deployed on-cloud in our organization.

To effectively use Docker, users should learn the basics of Docker and understand what containers and images are in Docker.

Overall, I rate Docker a nine out of ten.

We are currently migrating some of our applications to Docker containers on the tenant to improve their performance.

We have already started migrating one application to Docker and Kubernetes. We plan to complete this migration within the next two days. Additionally, we plan to migrate our core banking software to microservices, which will be containerized using Docker and Kubernetes.

Docker is useful for container virtualization and installation of applications. Docker is a containerization tool that enables the installation of applications without the need for virtualization. Its primary advantage is that it allows for more efficient utilization of resources, such as with Oracle virtualization. 

The key difference between Docker and classic consolidation is that the former does not rely on a physical machine for resource allocation. Instead, Docker creates lightweight applications that are easy to manage and scale, making the process faster and more efficient.

Moreover, Docker's scalability and manageability are the most valuable features for me.

There is room for improvement in terms of management. Because to use Docker, we should also use Docker as an orchestrator. But if Docker had the necessary tools for management, it would be very good.

I have been using Docker for one year. Moreover, I am using the latest version. 

It's stable because we just use it in a UAC environment.

It is a very scalable solution. It is one reason we plan to migrate to Docker. It is very scalable. We still have technical people working on it. Most of the admins can work on those solutions.

The initial setup of Docker is very simple and easy. If you know what you are doing, deploying the solution takes less than an hour. 

The deployment process depends on how the solution was developed. For Docker, you need to install it and then use Docker to get the necessary image for your OS. It keeps access and depends on your OS. 

Once Docker is installed, you can get the necessary image for your solution. The deployment can be done in-house. 

The licensing cost is not expensive. 

Overall, I would rate the solution an eight out of ten. I would recommend using Docker if you are looking for a scalable solution. 

We're utilizing Docker extensively as all our products and services are deployed on Kubernetes, which is based on Docker. Our reliance on it is high. We have various services, including Python, C++, and Node.js, and several applications that are deployed via Docker. Our usage of Docker is almost 100 percent across all entries.

The most valuable feature of Docker is that it revolutionized virtualization by providing a new approach with containers that completely nullified the time it used to take to deploy applications on virtual servers, resulting in deployment times that can be as quick as milliseconds, unless it is a heavy application, such as Java. Additionally, resource utilization has greatly improved with Docker, allowing for more resources to be allocated to other tasks. These are a few key features that make Docker a preferred choice.

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 have been using Docker for approximately 10 years.

Docker has various integrations, such as Docker, Compose, Docker Swarm, and Kubernetes, I have witnessed a considerable amount of downtime resulting in applications going down. Unfortunately, it has been difficult to pinpoint the root cause of these issues. Thus, I would say that Docker is not completely stable, with an estimated stability rate of around 90 percent. As a precautionary measure, I deploy my services on multiple stations with proper scalability and high availability to mitigate any potential downtime.

We only have engineering users using Docker which is approximately 50 percent of our staff. We have a total of approximately 25 people using the solution.

The solution is scalable.

The initial setup of Docker was easy but this has changed. The setup is not necessarily difficult, but it has become quite confusing. As long as I am familiar with all of the necessary commands and don't encounter any unexpected issues, it should be a relatively straightforward process. However, the written instructions are so convoluted that it may prove challenging to install everything without encountering any obstacles.

Docker has made some changes and there is an enterprise version that is affordable.

This solution is doing its job well. The stability could improve, but the other parts of the solution are great.

I rate Docker an eight out of ten.

We set it up a lot of times to create environments for our students. 

When we teach our students, it's really important that everybody is on the same version of all their dependencies. So, Docker, we can set up the images on Docker, and it sets everybody up. 

So it's a much smoother process. Without Docker, without these containers, it would be a nightmare trying to get 20 to 30 students to set up their environments correctly. So this is just a really quick and easy way to use it.

Just the portability of Docker's containers and its ability to give everybody the exact same environment and experience is most valuable to me. 

It could be easier to create images and save them on reports.

Just improved development workflow, just quicker, like some better user experience creating the images for the Docker containers.

We have used it every day in my current company just to set up our environment for our build processes. We create a lot of labs.

We use the latest Docker version 4.22.

It is a very stable product.

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

The initial setup was very easy. I use it on-premises as well as in the cloud. So we use it in both places.

It's free, as far as I know. 

Docker is very reliable. It's easy to scale, and it's very stable.

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

I use the tool for SQL, MySQL, and web development.

I think that with Docker, it is easy to deploy it on different platforms.

Stability is an area with a shortcoming. Hence, stability needs to be improved.

I have been using Docker for a year. Also, I don't remember the version of the solution I am using since it comes from the repository of Linux.

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

Normally, I use it on small sites, so I don't know if it can experience scalability.

More than 200 of my students use the tool. Also, the tool is used extensively by me.

Normally, Docker is free for everything, so I don't know if there needs to be a plan to increase the number of users.

Before Docker, I used only a Linux setup.

I have used Docker on Linux for the filesystem.

The deployment of the product was done in a minute or two, considering my internet is very stable.

I use the Docker control plane for the deployment.

I was involved in the deployment process of the solution.

Docker is a free tool.

I would definitely recommend the solution to those planning to use it.

I don't know what to say to those planning to use Docker, but you can find its details on the internet.

I rate the overall solution a nine out of ten.

I use Docker to create dev stacks, usually for developers to plug and play their applications, and in cases where they don't need to be bothered with complex architectures and decoupling services. We create a simple Docker compose file and provision it. We are customers of Docker and I'm a DevOps engineer.

The lift and shift is valuable because you create a lightweight image that can be accessed by anyone who has installed Docker.

I'd like to see improvement in some of the documentation because there are currently errors and it requires a thorough check and deep dive to make sure it's correct. If they were to incorporate what the community offers into the documentation, it would be beneficial.

Many people use multiple containers for their workload and it would be great to have pre-deployed solutions for typical deployments like WordPress and multiple CMS which would encourage more developers to use Docker. I would love to see the solution with pre-baked, ready-to-go capabilities for multi-container solutions.

I've been using this solution for five years. 

I haven't found such complex issues that I need to contact customer support. I found most of the answers through the community or using a work around. 

The initial setup is very easy. You just need some basic understanding of the system, and how containerization works. Images are already prepared so if the user doesn't have the images on his local system, Docker pulls it from the repository and it's good to go. It's much faster if the images are downloaded. As a DevOps engineer, I generally carry out the deployment myself. 

I recommend learning about containerization prior to using this solution starting with basic deployments. Take the opportunity to test it out and check the components. Docker has relieved a lot of the pressure, including the fact that I no longer have to provide everything from scratch. I know I just have to install the Docker community edition, make Docker images and get going. That said, Docker has some limitations and Kubernetes has discontinued using it. It's compatibility is reduced as a result and many organizations are moving towards Kubernetes and other orchestration services.

I rate this solution seven out of 10. 

In our company, I mostly design 5G networks and my work revolves around virtualization of the 5G core, which is known as backhaul. In our organization, we use many containerization technologies to obtain a proper ROI.

No-code servers and other servers are used in a combination predominantly as part of our company operations, which is the most relevant approach in the service provider or enterprise end. For small-scale customers of our organization, we use a combination of Kubernetes and Docker to drive adoption. 

One of the main use cases of Docker is resource utilization. Like traditional VMs, there is no need to depend upon reserving resources and it's much easier to spin up required instances for consumption using Docker. 

The capability of the solution to convert an application into a Docker image is a vital functionality. 

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.  

I have been working with Docker for almost four years. 

I would rate the stability an eight out of ten. Docker provides a highly stable environment to work with. 

I would rate scalability a five out of ten. In Docker, it's very difficult to predict how scaling works and this is where automation should be implemented. I would recommend Docker for small and medium-sized businesses as it provides a practical environment that can facilitate cost-savings. Docker also doesn't have critical workloads.

The applications used in critical workloads consume a high proportion of traditional server and physical infrastructure; by using Docker, the efficiency can be enhanced ten times. Docker is definitely a great option for small businesses that are trying to deploy applications on the cloud. Whether primarily deployed on-prem or cloud, with Docker the application can be moved in between them. 

I personally depend on the Docker community to resolve my issues with the product and avail support. 

The setup process of Docker is extremely simple. Docker is compatible with multiple operating systems, including macOS, Windows, and Ubuntu. 

I would rate the pricing of Docker as ten out of ten.  

OpenShift is gaining more popularity than Docker because it is used in enterprises that follow the traditional model. OpenShift is from Red Hat, and many enterprises are already running Red Hat-based systems at the back end, so it becomes much easier for them to move to OpenShift than to migrate to Docker.

For Docker based adoption, the entire existing infrastructure needs to be changed to migrate into the Docker environment but for OpenShift the older architecture just needs to be brought into the latest architecture. 

For container management, Kubernetes is our primary tool of choice in our organization, and we recommend the same for most of our customer's enterprise environments, but now we are witnessing a high adoption rate for OpenShift which has all the features of Kubernetes.

At our company, we are also noticing the rise of another competitor tool for Docker, which is called Amazon EKS, which runs on the cloud with a Kubernetes background. I can easily manage my public and private cloud using the same containerized environment and one single orchestrator. 

There are complexities in integrating Docker with other CI/CD tools because the available documentation is not straightforward. An expert is required with hands-on project experience to integrate Docker with other solutions. 

The solution should provide better deployment documentation with added project examples that can be used like a workbook by professionals. The vendor should develop and provide some explainer videos around Docker with a major focus on how AI has came to the picture and how Docker will provide integrations with automation and a Generative AI context. I have had two or three instances where I had used ChatGPT to deploy a code on behalf of me, but it took three of my colleagues to understand the AI-generated code. 

In recent days, I have noticed that enterprises are not adopting Docker, and they are choosing a solution like Proxmox. Other competitor solutions to Docker are easier to use, so the usability factor is causing the adoption of products other than Docker. But I would say Docker has a more mature environment than the competitors. 

The product is still at an early stage in terms of security. The basic aspects of security are covered, but there is a lot of room for improving the solution's security. Our organization works on container security and Docker should improve on container security. 

If you are working on Docker, you need to have expertise in the product, it's security, architecture and resource planning. I would choose OpenShift over Docker. I would overall rate Docker an eight out of ten. 

I'll definitely recommend Docker to users, especially to professionals who are working with a cloud-based environment, server-less architecture, or developers who are trying to build efficient applications. Docker is an excellent learning platform to initially get accustomed to basic architectures before shifting to more complex architectures like OpenShift.