Docker Reviews

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

Docker can be deployed on-premise or on the cloud.

We are using Docker for containerizing our applications.

The most valuable feature of Docker is that it provides a containerized environment. The isolation between the environments is beneficial. Additionally, the solution is easy to use.

Docker can improve the integration with Microsoft Windows. It does not support native installations. 

There can be a lot of issues with Microsoft Windows and Docker and those issues should be resolved in a future release. For example, if you are running Docker and you are running a lot of things in Microsoft Windows, these issues should be resolved.

I have been using Docker for approximately 

Docker is highly stable.

The scalability of Docker is very good.

Every machine learning group in my company uses Docker. We have approximately 2000 to 3000 people using it.

I have not needed to use the support from Docker because I have not had any issues.

The initial setup of Docker was extremely easy. The only part that takes some time is the containerization, the rest of the process is quick.

I rate the initial setup of Docker a ten out of ten.

Docker is a free-to-use solution. However, Docker Enterprise is not free.

We chose Docker over other solutions because it has a relatively large use user base. It is a popular solution.

If you are trying to use Docker for the first time, make sure that the Docker file you have or the containerization which is done, is done properly. If the containerization is not done properly there can be some folders that are not mounted correctly and it causes several issues.

Docker Enterprise takes less time to set up if I was to compare it to this Docker free open-sourced version.

I rate Docker a nine out of ten.

In our case, Docker is a prerequisite to deploy on Kubernetes. We utilize and integrate Docker along with Jenkins. When we trigger the pipeline, it triggers and runs the Docker build to create the image. It's a JAAS service. Before deployment, everything is on a non-AWS platform. Once the image is created and deployed on Kubernetes, it will be hosted on AWS. 

We started creating images on Jenkins as a service, which is on a different cloud. Once it's deployed on Kubernetes, it's placed on AWS. We have also deployed the Artifactory server using ECS.

It's deployed on the cloud. The cloud provider is AWS.

The security layer is very vulnerable, although they are working to improve the system hardening and image hardening. They need to provide a simple solution for a user to implement these two security features while creating the Docker image. It's not easy for simple users. 

I'm part of the operations team, so I understand how Docker images are created using Unix features. Docker itself creates a snapshot of the existing infrastructure. Docker's features should be simplified enough so that developers can understand and implement them. 

I have worked with Docker for eight years.

I would rate the stability as five out of five. I have seen end-to-end performance with Docker. It's a great tool, and it's the most popular container service in the market.

It's not very scalable. In order to handle scalability, Docker Swarm is the available solution with Docker. Docker Swarm is another service, but it isn't stable. For multi-containers, they have introduced Docker Compose. One deployment set will trigger multiple containers. There isn't a scaling feature, but a single host can run multiple containers.

I would rate the scalability as two out of five.

Installing Docker on individual systems is pretty simple. Docker needs to be installed for each user so they can access Docker testing, MS testing, and deployment testing.

I would rate setup as five out of five.

Deployment was done in-house. Three people were needed for deployment. We have two people for maintenance.

Deployment was basically done by the IT team. We just needed to create a ticket to trigger the deployment from the IT team. It's pretty simple.

We pay for a license. To make it more scalable, you need to pay for Docker Swarm, which is an additional cost.

If an organization utilizes a service free of cost, then the cost of Docker is like overhead for an organization. Docker was freeware, and they started asking for licensing costs about seven months ago. As soon as that news was published, many organizations started thinking about other free container services. 

My company started uninstalling Docker from everybody's system to minimize the cost, and the proof of concept for other container services is still in progress. For commercial use, it's about $30 per month. The license itself isn't expensive, but if there are many users, the price becomes high.

My company is thinking about different open source solutions.

I would rate the solution as eight out of ten. 

Docker is a prerequisite for utilizing Kubernetes. If somebody doesn't have experience with Docker, then they can't create the Docker image. Having the application image is a prerequisite for deploying on Kubernetes. 

Once we started utilizing Kubernetes, the official website recommended using Docker as a container service, but now they've removed that recommendation. You can utilize any of the available container services in the market.

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.

We are using Docker in our Java pipeline which is based on DevOps.

We use Docker because we do not have to set up an environment to let people try applications.

Docker could improve by having security vulnerability reports.

I have been using Docker for approximately two years.

Docker is a stable solution, but there are some security vulnerabilities and that's why we are using security tools to point out if any vulnerabilities arise.

The scalability of Docker is good.

We have most of our application running using Docker in our organization and there are over 1,000 people using the applications.

I have not contacted the support from Docker.

I have previously used Prisma but I found Docker has more features.

The initial setup of Docker can be easy. However, it depends on the network you have Docker on.

We have Docker configured everywhere and it took approximately one hour.

There is a license needed to use Docker.

My advice to others is they should use this solution. Previously we had to set everything up for small deployments in the environment, but with Docker, we can directly run the application in a container and pull any images. We don't need to set it up. We can use an image and we can directly set it up.

I rate Docker an eight out of ten.

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.

I think the best feature is to replicate anything in our local machine using a simple command. 

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 have been using the tool for four years. 

The solution is stable. 

The tool is very easy to scale up. My company has 100 percent usage for the product. 

I have never contacted the support. I always look at GitHub instead of raising a ticket. 

The product's setup is easy and straightforward. However, you will encounter difficulty in customization. The speed of the product's setup depends on the bandwidth and download speed. 

The product is a free open-source tool. 

I would rate the product a nine out of ten.