Docker Reviews

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.

Docker is an open-source container runtime for running container images. We are using Docker Swarm which is similar to Kubernetes but from Docker.

The most valuable features of Docker are its security, detailed documentation, and ease of use, and the Docker Swarm is not as complex as Kubernetes.

There is a feature called overlay network for orchestrating containers in Docker Swarm which makes everything easy. You don't need a load balancer, which makes everything easy for accessing in one container. Additionally, it has internal DNS, which is not in Kubernetes.

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.

I have been using Docker for approximately six years.

The performance of Docker is good. We usually follow best practices before deploying Docker, we have not had any issues since deployment.

Docker is scalable. However, If you want to vertically scale, you have to do it manually. It doesn't have autoscaling.

We have seven people using Docker in my organization.

The support from Docker is very good. The documentation is rich, any issue you face, somebody already faced and the information is available.

The main reason we are using the Docker Swarm instead of using Kubernetes is you can set up Docker Swarm within five minutes. Docker is easy to set up. Once you install it, you can run it. In this case, the container runtime becomes Docker. The reason why we are using it is the vendor recommended Docker for bank sector purposes. 

Setting up the master nodes in Docker is very easy.

Docker is a free open-source solution. However, there is the Docker Enterprise which is a paid solution.

The founder of Docker decided to move to Docker Enterprise to make revenue. There are many people moving away from Docker.

My advice to others is if you are using legacy applications they do not run well with containers. The person wanting to use Docker has to ask themself questions about themselves to determine if this solution is best. For example, the application that they want to run has to be scalable. People think Docker or Kubernetes is going to solve their problems, but no. If you have problems, it's going to amplify them, but if you have easy, smooth applications, it's going to make your life easier. The application itself has to be scalable. 

The application has to be container ready, such as login inputs, does it follow the 12-Factor principles of deployment, and has security. Even if you don't have security, Docker can help with security if you don't have application security.

You need to consider how you are going to patch the images or the applications and if it will work with languages on WiFi, such as Java, Python, or Ruby version.  Those are requirements you need to meet before deploying Docker. You have to find answers to many questions.

I rate Docker a seven out of ten.

I gave my rating a seven out of ten because autoscaling is necessary for cloud-native applications and it is not available. However, it's easy to use, scalable, and straightforward. It was the defacto container runtime for a long time until they went to an enterprise. Docker is very good in CI/CD. Anybody building images is using Docker to build the images and it works well with CI/CD.

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. 

Containerization is one of the use cases of Docker. Basically, Docker provides containers to its users. So, users can build, run and share containers among developers.

Feature-wise, Docker is very user-friendly. Also, though the solution may look basic, it is a very relevant one in the market owing to the functionalities that it provides to its users.

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.

I work in an IT company, and we are currently working on a distribution model. So, we are the distributors for Docker. Hence, we are not using Docker much and are involved in selling it. So, my company has been associated with Docker since the time it started its business.

It is very stable. So, the tool is as stable as it can get in terms of containers.

Regarding the solution's scalability, it can be automated, but Docker does not have that automation feature. So, its integration process can be carried out with an infrastructure automation tool like Terraform. In short, scalability is one of the features that Docker offers for anything with containers or anything you're running in containers.

Regarding our customers who are using Docker, I would say that we have a great and huge market share. Even though I feel that Docker's market share is around 90%, it could be more than that.

Docker provides all the technical support to its users, especially to those who purchased a Docker license, which comes with a basic SLA agreement. It means the technical support is covered directly by the vendor. Docker has a team of engineers who work in its technical support team serving globally 24/7.

The solution's initial setup process was straightforward. Basically, it is an open-source product, so one does not have to worry about the setup process since it's as basic as it can get. So, our company does not have to position the solution with the customers because they already use it. We just have to make sure the customers are shifted to the enterprise version of the solution so that our company can make some money.

The solution can be deployed on the cloud or on-premises, so our customers can choose a hybrid model.

Regarding the deployment process, one can directly download Docker from their official website, making it very straightforward. Also, I am unable to elaborate further since I have never personally deployed the solution as a salesperson.

Regarding the deployment and maintenance of the solution, any developer can deploy it. So, even you or I can try to deploy it since it is very straightforward.

Customers pay for the license through a yearly subscription model, where they pay per license. This means that the license is based on a subscription, and the customer pays annually for each license they use. If you consider the features that Docker provides to its users, I would say that the solution is affordable.

Docker is considered to be a flagship product when it comes to containerization. If a person is going to run containers for developers, Docker should probably be chosen. Docker's enterprise version is also a great solution. For any enterprise organization that is running containers or building or developing application containers, Docker will offer some great features that allow a person to collaborate with the whole development team and manage everything. Docker provides its users with the functionality to control and manage everything. Since Docker is the best solution in terms of containerization, I rate the overall solution a ten out of ten.

We use Docker to build pipelines and deploy applications. We primarily use it to create application images that we deploy on Kubernetes Podass. The solution is deployed on-premises and via a private cloud.

The solution is lightweight which is valuable. Additionally, the ease of deploying on any cloud is valuable.

I rate the solution a nine out of ten. The solution is very good, and I am unsure how it can improve further. I advise new users to review their website, commands, and the steps for creating images.

We have been using Docker for approximately one year.

The solution is stable.

The solution is scalable. Currently, we have approximately 300 employees in development utilizing the solution.

We do not have experience with customer service and support.

We chose to use this product because of its stability and because of reviews from people who previously used it and had no issues.

The initial setup was easy, and you are only required to run commands.

Our primary use case is to build and bundle applications.

The most valuable feature is that it gives you the same environment as on a developer machine as well as a production machine relevant to specifications. The binaries and dependencies are all bundled together and they are in a similar fashion in both places.

I would like to see better management layers. One example of this would be binary shipping. I would also like to see Docker utilize a concept like Red Hat Family.

I have been using Docker for three to four years.

The stability is excellent. Sometimes, memory management can be tricky.

Docker is scalable on both community and commercial levels. I am using the community version. There are around one hundred to one hundred and twenty of us using Docker on a daily basis.

For customer support, we are using the documentation on the forums and they are suitable.

The initial setup was very simple and straightforward.

You can use either an in-house or vendor team. We simply downloaded Docker into our organizational environment.

There are a sufficient number of YouTube videos and best practices to build Docker. I would encourage a potential user to investigate those videos. On a scale of one to ten, I would rate Docker a nine.

We used to have a silo problem. Docker solved it because we're able to containerize the microservices that we're developing in the form of Docker mail.

Once we run the Docker image, it becomes a container. This container is guaranteed to run in every machine because we're installing Docker as the platform. On top of Docker platform, we're curating the Docker images and running the container. That container has a limited number of libraries and a limited number of data, which is required to run the application.

Each container has a limited library system, which is required to run the application. This encapsulation makes it work perfectly, irrespective of the system. It works perfectly once we have encapsulated the application and containerized it. This is guaranteed to run in each machine.

We're deploying the solution on Azure cloud. We're curating the CI/CD pipeline. In the CI/CD pipeline, we're curating the Docker images and pushing it to the container registry. We're writing the steps for how to build the Docker image into the YAML code. Once the Docker image is built, it's pushed to the container registry. We're writing this YAML code in the pipeline.

Every person on the DevOps team is using this Docker tool.

We have plans to increase usage because it's a great tool, and it's the latest technology. We're no longer developing monolith architecture, so everyone is developing applications with microservices. Docker is the best tool to containerize the application and encapsulate it.

We used to work on monolithic architecture to develop the application until it goes to the production environment. It takes a huge amount of time. Now, we are using a microservices architecture. Rather than creating the application as a whole, we are dividing the application into small services. Each microservice is loosely coupled. With each microservice, we can develop and containerize it in the form of a Docker container.

If an application has a hundred microservices, like on an e-commerce portal website, then the login is usually one application, the catalog is one application, and the E-card is one application. Each application can be considered as one service. For each microservice, we can develop a code and containerize it.

Containerization is the most valuable feature. I can communicate to the Docker containers using other containers. The copying feature is helpful because if a container dies, we won't lose the data. That data is retained because of this data volume feature. We mount it to our shared system or any shared folder.

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.

I have used Docker for four years.

I would rate the stability as seven out of ten.

I would rate the scalability as seven out of ten.

I would rate technical support as seven out of ten.

Setup is simple. We can install Docker with just one command. It doesn't take more than three to four minutes to run the pipeline. A Docker image is built in that time frame.

We're running the pipeline in a self-hosted agent or Microsoft-hosted agent.

Docker Compose can be installed easily. It allows you to use multiple containers at a time. Docker Swarm can also be installed easily.

Docker is open source. To use a Docker enterprise model, we would need to pay for it.

I would rate this solution as seven out of ten.

My advice is to create an account on Docker Hub. In Docker Hub, there are three Docker images available for practice. We use GitHub to see how we're making the Docker images and then push it to the public Docker Hub. I have an account in Docker Hub and have images there that I can reuse later. I would also advise completing a Udemy course for Docker or watching YouTube videos about it. This will make Docker easier to understand.

Our primary use case for this product is for packaging our solutions. In addition, we use it for packaging our web apps and deploying them on public cloud, primarily on Azure.

The simplicity is valuable.

Deployment could be quicker and customer service and support can be improved.

We have been using the solution for approximately five years.

The solution is very stable.

The solution is not very scalable on its own, but when used in conjunction with Kubernetes, it is seamless because it integrates very well. Kubernetes was made for Docker, so, understandably, they work well together.

I cannot comment on pricing specifics, but we currently use the open-source version of the solution, so it is primarily free. We pay just for bits that are in their new pricing.

I rate the solution a nine out of ten. I advise users considering the solution to learn how to use it as soon as possible so they can easily conduct deployments.