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

I use Docker to create dev stacks, usually for developers to plug and play their applications, and in cases where they don't need to be bothered with complex architectures and decoupling services. We create a simple Docker compose file and provision it. We are customers of Docker and I'm a DevOps engineer.

The lift and shift is valuable because you create a lightweight image that can be accessed by anyone who has installed Docker.

I'd like to see improvement in some of the documentation because there are currently errors and it requires a thorough check and deep dive to make sure it's correct. If they were to incorporate what the community offers into the documentation, it would be beneficial.

Many people use multiple containers for their workload and it would be great to have pre-deployed solutions for typical deployments like WordPress and multiple CMS which would encourage more developers to use Docker. I would love to see the solution with pre-baked, ready-to-go capabilities for multi-container solutions.

I've been using this solution for five years. 

I haven't found such complex issues that I need to contact customer support. I found most of the answers through the community or using a work around. 

The initial setup is very easy. You just need some basic understanding of the system, and how containerization works. Images are already prepared so if the user doesn't have the images on his local system, Docker pulls it from the repository and it's good to go. It's much faster if the images are downloaded. As a DevOps engineer, I generally carry out the deployment myself. 

I recommend learning about containerization prior to using this solution starting with basic deployments. Take the opportunity to test it out and check the components. Docker has relieved a lot of the pressure, including the fact that I no longer have to provide everything from scratch. I know I just have to install the Docker community edition, make Docker images and get going. That said, Docker has some limitations and Kubernetes has discontinued using it. It's compatibility is reduced as a result and many organizations are moving towards Kubernetes and other orchestration services.

I rate this solution seven out of 10. 

The solution is used to run systems in small applications.

You should start by running your applications to ensure optimal performance in a Docker environment. The administrator should validate the setup with Kubernetes before deployment. This process includes validating our software applications and comparing features with other open-source alternatives. It’s important to understand that application performance can vary due to various factors. For instance, issues may arise due to ZDR policies. Before deploying in production, consider using OpenShift if additional features are needed. Our organization currently uses Oracle, but Docker provides a flexible and efficient way to manage our applications.

We use Docker to facilitate deployment, updates, and management.

Enhancing artificial intelligence capabilities and cluster management should be a priority. It should facilitate some security management.

I have been using Docker for four years.

I have been going through the session block for enhancement. I rate the solution’s scalability a six out of ten.

The initial setup is straightforward.

It requires a premium subscription.

The CI/CD was created, and the template is there. It's sufficient to prevent blockers. The restore is deployed, and we are conducting large-scale scans to identify duplicates. For continuous intelligence, we are using Azure DevOps tools from GitLab. We use Docker for various tasks like scanning, automation, testing, and searching.

We support software implementation and maintenance. Nowadays, we update our software regularly. Our recommendation for regular users is to avoid using outdated software, especially when it involves personal data sources such as software applications, desktops, and internet usage.

Azure uses Docker and integrates with Azure products. Docker overlaps the network, which facilitates communication between containers. This network operates on VPNs but can utilize third-party gateways to reach and solve problems.

Docker has more advanced authentication, backup, and accountability.

Overall, I rate the solution a six out of ten.

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. 

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.

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.