Docker Reviews

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. 

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.

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

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.

I'm using Docker local Kubernetes development. I'm building software that uses Docker for cloud and on-premises applications. I'm consulting for a company that provides an enterprise database solution built using Docker containers and Kubernetes, so everyone at the company is using Docker indirectly.

Docker packages up an application as a single item that you can then run without the need to install or configure it to work on any specific machine.

The command line interface could be more intuitive. I constantly struggle with it. 

I have been using Docker for three or four years.

Docker is stable.

Docker is scalable for the most part. But we have had issues where we ran out of disk space, and it doesn't work. When I say "disk space," I mean the space that Docker has allocated. Docker isn't scalable on its own, but it is if you're using it with something like Kubernetes.

Deploying Docker is pretty easy. 

An enterprise license costs $24 per user per month. For a team or a smaller license, it costs $9 or $5 per user.

I have looked at some of the newer ones that came out. We looked at Podman, but it didn't have the API that we needed. We also looked at Rancher. When I was at HPE, Docker started charging a license, so management decided to switch to something else because they didn't want to pay for it. After about six months and lots of wasted time and effort, they realized that it was worth paying for it. 

I rate Docker 8.5 out of 10.  From a business perspective, Docker is the de facto standard, and it's going to cost you less to use it than to try to find an alternative unless there's something that Docker can't do. It's going to cost you less because there are so many more free resources available. Your team can Google and find technical information much more easily about Docker than any other solution.

The advice I'd give to someone who is new to the solution is to find an online course that can walk you through Docker because it can be really confusing to get up to speed on it.