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.

In our line of work, we've been involved in various sectors, such as industrial products, transportation, client engineering, telecom, and medical. For instance, we're currently developing an IT platform. One key use case we're tackling is device management.

We're looking at managing devices within our setup. These devices send data or signals, which then get transferred to the cloud. It's all about handling the lifecycle of these devices, deploying them, and managing non-provisioned ones, both on our end and on the client's side.

Docker needs to improve its pricing. 

I rate Docker's stability a nine out of ten. 

One of the primary reasons we use the tool is its scalability. It scales easily, and we haven't had any issues with it.

Docker's support is user-friendly, fast, and knowledgeable. 

The tool's deployment difficulty is medium.

It tends to make sense as an investment for larger enterprises, but the cost might seem expensive for smaller businesses.

We use the solution for containerization. We've replaced it with other solutions. We are using it to compartmentalize some legacy products. We are also onboarding other third-party applications using it. We have a few use cases. 

It's helped to save many resources.

The features, such as scaling and high availability, have been excellent. 

It is easy to set up. 

The solution is stable.

It can scale well. 

The pricing could be a bit better. We'd like the least amount of spend as possible.

We'd like knowledge transfer to be easier.

The support could be better. 

The solution can be a bit expensive. 

I've been using the solution for about six years so far. 

The solution has been pretty stable. 

The solution can scale well. 

I'm not sure how many users are currently using the solution. We are migrating all development teams over to containers. 

We have support from our vendor and also use support for the Kubernetes cluster. It could use some improvement. It could be a bit better. They should be more responsive. 

I've been working with Kubernetes alongside other solutions. 

The implementation, for me, was pretty simple. I'm not sure if others would have issues. 

I would deeply it on top of the Kubernetes cluster. It usually takes one day to deploy. We're using Docker as a service for testing purposes and have implemented it on Kubernetes clusters in order to test and deploy applications in order to handle production-grade applications. 

Have not looked into ROI to see if we have witnessed any. 

I'm not sure what the exact pricing is. I don't deal with licensing. However, my understanding is it is expensive. 

I started using the trial version and moved on to the latest version. 

I'd recommend the solution to others. I'd rate it nine out of ten. 

We use Docker to build, run, and ship any application.

The solution's most valuable feature is container registry interface.

They should provide proper documentation to understand the solution's cgroup and other processes.

The solution is stable. Although, it consumes a lot of battery and RAM to create virtualization on macOS.

We have ten solution users in our organization. Its scalability for multiple VMs needs improvement.

The solution's customer service is good.

Positive

We were using VMware as well. In comparison, Docker is easy to use, consumes fewer resources, and takes less time to complete the process.

The solution's initial setup process is easy. It takes less than an hour and requires one person to execute. Also, it is easy to maintain because we can see logs.

I use the solution's open-source version.

I advise others to use JPT to create docker images. They should know the basic process for it. I rate the solution a ten.

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.

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.

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.