Docker Reviews

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. 

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.

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. 

We are a service provider and we have various use cases. However, the most prominent one is that instead of virtualizing the application workloads, we use Docker. Docker allows you to create small applications and containerize them. You can create multiple such application containers that can run simultaneously on the Linux operating system.

We use Docker because if we want to create an application using Node.js, an environment for backend and frontend technologies, we can deploy this single application in a container. This container will run independently of its underlying OS. 

If you want to migrate this application to a different server, migrate the container image to the new server and start using the application there. This makes developers' jobs much easier because they don't have to copy everything the application needs. They just copy the container image, send it to a different server, and start using it there. All the required libraries, packages, and dependencies are encapsulated within that container. The container contains everything it needs to run. In a DevOps environment where multiple teams are creating applications, developing new versions, and deploying applications frequently, Docker is very helpful.

The greatest benefit of the solution is that you can create applications and multiple versions of the same application, distributing them across various Linux platforms. Setting up Docker is very quick; whereas setting up a Linux operating system can take five to ten minutes, you can set up a Docker-based Linux OS container within minutes. Docker also has a small footprint on memory and resources because it uses the system's resources efficiently. It operates within its environment, independent of the underlying operating system, running in its namespace. This isolation prevents negative impacts on the system.

For developers who frequently create and deploy applications, Docker makes it easy to quickly develop, deploy, and run the latest versions. You don't need to manage the operating system, applications, dependencies, or data separately; everything is encapsulated within the Docker container itself.

Moreover, AI is another application you can use through Docker. AI can help you set up more efficient Docker-based workloads. The role of AI is to guide you and provide the necessary knowledge for various tasks, whether it’s related to Docker or anything else. Additionally, AI itself can run as a container using Docker.

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 solution’s stability is great. I rate it a nine out of ten.

Regarding scalability, Docker doesn't require any separate configuration for multiple users. Suppose you create a container and expose it to the public via an IP address and port. The ability to serve the number of users depends on the system's resources, like RAM, CPU, and storage. You can create or scale the number of containers based on these resources, and manage the number of users accordingly.

For example, if I have a small server, I can create containers and share them with the outside world according to the available resources. The server's ability to handle the number of users depends on its resources. Docker doesn't restrict you to a certain number of users; hundreds or even thousands of users can access the containers. Most of our customers are using the product.

The initial setup hardly takes minutes. All the container images are available on Docker Hub when you create a container. Docker Hub is a repository, like an App Store for containers. If you use Windows or Mac, you have an App Store where you can download and start using any application you want. Similarly, Docker Hub is the application store for containers. It's a cloud-based solution. In Docker Hub, you can find all kinds of container images. If you want to install an Apache server, a Postgres database server, or any other server—even Linux and Windows servers—they are all available in containers. Anyone who wants to use these can immediately download and start using the container image.

Our customers buy the software and the prices are available on Docker Hub. The subscription is typically yearly, and customers will need to buy the subscription directly. They can purchase it themselves.

The product is similar to GitHub.

If you are trying to create an application quickly for testing or development purposes, Docker is the best tool available. Docker can also be used on Mac and Windows with a tool called Docker Desktop. You can start using Docker there by installing Docker Desktop on a Windows or Mac system.

Whenever a new Docker image is created by the OEMs, like MySQL for instance, they name the new image with the version number. If you want to check the latest version, you can go to Docker Hub and search for it. There are multiple versions available, and Docker also allows you to create your own version. So let's say your company has specific requirements for MySQL. You can download the original MySQL image from Docker Hub, install a couple of additional applications within the Docker container, and share this customized Docker image via your own repository on Docker Hub.

There are two kinds of updates: one within the Docker technology itself, where the creators of Docker keep updating the Docker engine, and another for the Docker images. The Docker engine is the software tool that runs on your system, and the global team working on it keeps it updated. You can always check for the latest version of the Docker engine and upgrade as needed.

Moreover, container orchestration is a different technology. You need Kubernetes to orchestrate the containers in the solution. A single container is independent, but Kubernetes is an orchestration tool that manages these containers using its control and data planes. For example, if you have hundreds of containers, it takes work to manage each one independently. You need some orchestrator to control these containers' life cycles, maintain high availability, and more. Kubernetes handles this container orchestration.

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

The solution is used to run systems in small applications.

You should start by running your applications to ensure optimal performance in a Docker environment. The administrator should validate the setup with Kubernetes before deployment. This process includes validating our software applications and comparing features with other open-source alternatives. It’s important to understand that application performance can vary due to various factors. For instance, issues may arise due to ZDR policies. Before deploying in production, consider using OpenShift if additional features are needed. Our organization currently uses Oracle, but Docker provides a flexible and efficient way to manage our applications.

We use Docker to facilitate deployment, updates, and management.

Enhancing artificial intelligence capabilities and cluster management should be a priority. It should facilitate some security management.

I have been using Docker for four years.

I have been going through the session block for enhancement. I rate the solution’s scalability a six out of ten.

The initial setup is straightforward.

It requires a premium subscription.

The CI/CD was created, and the template is there. It's sufficient to prevent blockers. The restore is deployed, and we are conducting large-scale scans to identify duplicates. For continuous intelligence, we are using Azure DevOps tools from GitLab. We use Docker for various tasks like scanning, automation, testing, and searching.

We support software implementation and maintenance. Nowadays, we update our software regularly. Our recommendation for regular users is to avoid using outdated software, especially when it involves personal data sources such as software applications, desktops, and internet usage.

Azure uses Docker and integrates with Azure products. Docker overlaps the network, which facilitates communication between containers. This network operates on VPNs but can utilize third-party gateways to reach and solve problems.

Docker has more advanced authentication, backup, and accountability.

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

Currently, we are creating a JAR file and using microservices. There are around 178 services in a single project. We use Docker to manage and do load balancing for all the services together.

We are using Docker to host applications. We are using Docker Compose and sometimes Docker Screen.

We are facing multiple issues with the solution's stability.

We have been using Docker in the same project for five years, and we have recently deployed Docker into Kubernetes for four years.

We are facing multiple issues with the solution's stability. It is very difficult to analyze how much load a tool takes. Sometimes, our Docker images get crashed due to the unavailability of space.

I rate the solution a six or seven out of ten for stability.

Approximately, 400 users are using the solution in our organization.

I rate the solution a nine out of ten for scalability.

The solution’s initial setup is simple.

We implemented the solution through an in-house team. It took me around three to five hours to deploy the solution. Docker is easy to use and implement. For the deployment process, we used Docker in the CI/CD pipeline. Then, we pushed the Docker images to the Kubernetes as per the environment. We used Kubernetes to host and balance the load.

Since Docker is an open-source solution, it is free of cost.

Docker made it easy for us to monitor the microservices. Secondly, we were able to manage the key load balancer. Thirdly, we wanted to create a secure layer of protection for our organization. So, we started using the containers above the hypervisor.

It was like using a new operating system. We created our own network adapters. We created another isolated network inside the Docker containers to keep our organization and project safe and secure. We consider this very helpful in the secure software development life cycle.

We're implementing multiple stages in security. We are signing Docker images, Docker containers, Kubernetes containers, Kubernetes nodes, and clusters in cryptography. We are signing these so that no one tampers with the code or the docker images. We are doing this from a security point of view.

The solution's containerization helps us in providing integrity and availability. If you use a microservices architecture, I recommend implementing Docker and Kubernetes. I would recommend Docker and Kubernetes to manage multiple microservices running simultaneously.

We had to configure multiple services, like the utilization of the CPU and the utilization of the RAM for the service that we were building. Additionally, we had to mention the network adapters we will be using. We followed multiple benchmarks, like NIST Benchmarks and CIS benchmarks.

There were multiple advantages to using Docker. The most important advantage was scalability and availability. As I am working in the security team, I'm looking after the integrity of the Docker images.

Overall, I rate the solution an eight out of ten.

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.

Docker helps us implement applications quickly.

Docker is convenient and easy to use. We can create and implement different types of virtual machines. It provides a lot of flexibility. The applications can be deployed quickly.

The stability could be improved.

The product is stable and reliable. I rate the stability a nine out of ten.

Five engineers in the IT team use the product in our organization.

The support team is fast, customer-friendly, knowledgeable, and quite professional.

We didn't face any issues with the installation.

We deployed the tool in-house.

The tool provides a return on investment. We are able to deploy some services and applications faster and be aligned with business requirements.

We have a monthly subscription. The product is not expensive. I rate the pricing an eight out of ten.

We do not use the solution often. It works well. We don’t have huge projects. I will recommend the tool to others. Everyone in IT uses Docker. Everyone knows it. At some level, a company must find a way to use Infrastructure as a Service by implementing different container technologies like Docker. Many IT personnel are aware of the solution. Overall, I rate the tool a nine out of ten.