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.

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.

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