Docker Reviews

We normally use Docker for building and testing all of our applications in a much faster way. We create the software as packages and then use Docker to create containers to build these packages. This process allows us to run and manage our applications.

The tool helps us in code versioning. I think it's pretty much easy to use and very straightforward. Even if someone is new to the tool, they can easily start using it with a little guidance or theoretical knowledge. Go through the tool and start using it without much struggle.

Docker reduces our efforts. However, from an AI perspective, we haven't explored it extensively yet. We need to start incorporating it more. Currently, our version doesn't utilize Docker heavily for AI tasks, but we plan to revise and implement our model in the future.

Sometimes, we have sync-up issues where the build doesn't get processed due to these sync issues, causing the build to fail. That's one of the drawbacks I see. When we did a huge sync-up, we faced a couple of issues. It takes some time for us to complete the sync-up. For frequent, smaller updates, we haven't had any issues. However, challenges can arise for those who prefer doing everything in one go. This might not necessarily be due to the tool itself but because of the approach of doing everything in a single batch.

I have been using the product for eight to nine months. 

I rate Docker's stability a nine out of ten. It's a good product because it simplifies everyone's work, whether related to coding, testing, or integrating with multiple parts and management.

I rate the solution's scalability a nine out of ten. My company has eight to nine users. 

The tool's deployment can be a challenge. It can be a bit challenging if someone is completely new and has never worked on it before. It has too many steps. Ideally, it can be finished quickly in about three or four steps.

An integrator helped us with the deployment. 

Docker streamlines our workflows and provides faster results. It simplifies our software dependencies, enhances productivity, and enables easy sharing and collaboration across different ALM models. 

I rate the overall product a nine out of ten. 

I use Docker for containerization, deployment, and to create packages. Docker has a wide range of uses and integrates well with other command-line tools like Terraform. Docker is most helpful when trying to work with CI/CD pipelines.

Docker's containerization property is its main selling point.

I'd like to see the new update on containers and what you can achieve with the new version of Docker by using containers. I would also like to know the range of applications for which it can be used. I want to see if new architectures have been incorporated in Docker or if we have to wait for another release.

I have been using Docker for one year.

I rate Docker a nine out of ten for stability.

Docker is a very scalable solution. I rate Docker a nine out of ten for scalability.

Docker's initial setup is straightforward. As a command line tool, it also provides you with docks to reference if you get stuck or have issues.

The solution's deployment time depends on your internet latency or internet speed and the size of the container. If you are deploying a very large application, it will take some time to set up.

Docker is deployed on-cloud in our organization.

To effectively use Docker, users should learn the basics of Docker and understand what containers and images are in Docker.

Overall, I rate Docker a nine out of ten.

I use the tool for SQL, MySQL, and web development.

I think that with Docker, it is easy to deploy it on different platforms.

Stability is an area with a shortcoming. Hence, stability needs to be improved.

I have been using Docker for a year. Also, I don't remember the version of the solution I am using since it comes from the repository of Linux.

I rate the stability of the solution a nine out of ten.

Normally, I use it on small sites, so I don't know if it can experience scalability.

More than 200 of my students use the tool. Also, the tool is used extensively by me.

Normally, Docker is free for everything, so I don't know if there needs to be a plan to increase the number of users.

Before Docker, I used only a Linux setup.

I have used Docker on Linux for the filesystem.

The deployment of the product was done in a minute or two, considering my internet is very stable.

I use the Docker control plane for the deployment.

I was involved in the deployment process of the solution.

Docker is a free tool.

I would definitely recommend the solution to those planning to use it.

I don't know what to say to those planning to use Docker, but you can find its details on the internet.

I rate the overall solution a nine out of ten.

We're utilizing Docker extensively as all our products and services are deployed on Kubernetes, which is based on Docker. Our reliance on it is high. We have various services, including Python, C++, and Node.js, and several applications that are deployed via Docker. Our usage of Docker is almost 100 percent across all entries.

The most valuable feature of Docker is that it revolutionized virtualization by providing a new approach with containers that completely nullified the time it used to take to deploy applications on virtual servers, resulting in deployment times that can be as quick as milliseconds, unless it is a heavy application, such as Java. Additionally, resource utilization has greatly improved with Docker, allowing for more resources to be allocated to other tasks. These are a few key features that make Docker a preferred choice.

There may not be much room for improvement with Docker as it has greatly evolved. However, one area that could be improved upon is the documentation on their website which was once easy to follow but has become quite terrible with numerous versions being released. As an example, the installation process for Docker now requires more than just a one-line command, causing inconvenience. Additionally, based on my experience as a college instructor, teaching students to install Docker was a difficult task due to the lack of straightforward and easy-to-follow documentation. Docker should focus on improving their documentation to make it more user-friendly for all.

In an upcoming release of the solution, the UI should be made even more user-friendly and comprehensive, as it currently requires a multi-step process to set up a registry or host a container. A one-click solution that streamlines the entire process and makes storing, leaving, and cleaning up images significantly easier. This feature would greatly benefit those who have previously struggled with additional cleaning when hosting their own container, and it would make the end-to-end Docker experience more accessible and efficient.

I have been using Docker for approximately 10 years.

Docker has various integrations, such as Docker, Compose, Docker Swarm, and Kubernetes, I have witnessed a considerable amount of downtime resulting in applications going down. Unfortunately, it has been difficult to pinpoint the root cause of these issues. Thus, I would say that Docker is not completely stable, with an estimated stability rate of around 90 percent. As a precautionary measure, I deploy my services on multiple stations with proper scalability and high availability to mitigate any potential downtime.

We only have engineering users using Docker which is approximately 50 percent of our staff. We have a total of approximately 25 people using the solution.

The solution is scalable.

The initial setup of Docker was easy but this has changed. The setup is not necessarily difficult, but it has become quite confusing. As long as I am familiar with all of the necessary commands and don't encounter any unexpected issues, it should be a relatively straightforward process. However, the written instructions are so convoluted that it may prove challenging to install everything without encountering any obstacles.

Docker has made some changes and there is an enterprise version that is affordable.

This solution is doing its job well. The stability could improve, but the other parts of the solution are great.

I rate Docker an eight 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.

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.

When we are developing an application, we try various libraries. It is better to isolate one application from the other because if they install one library and then it doesn't work on the other end or while using a driver, then it doesn't work on the other driver. There is always this conflict that is bothering us, and that is where Docker separates containers to build applications.

Docker is a useful tool that we just implement and use directly.

It is a perfect solution for me stability-wise. Owing to a few shortcomings in its stability, I would say that its stability can be improved. It is important to note that I am not an expert to speak about what needs improvement.

In the future releases of Docker, we should be able to isolate a couple of applications. It should also be possible to isolate an environment.

I have been using Docker for one or two years.

The solution is stable.

The solution is scalable.

We have a couple of users in our organization using Docker since it's just a test system right now.

We don't have plans to increase usage.

We haven't contacted the technical support of Docker. We did search for the details of Docker's support team on Google.

We have used the virtual machine named VMware previously. We switched to Docker because VMware was very clumsy when we tried to build a lot of virtual machines using it. VMware is best suitable as a business solution.

The initial setup of the complete environment is complex, but Docker is easy to set up.

If you want to set up a complete environment, it will take a week, depending on the applications.

We don't do the deployment since we only look into the PoC phase. The company we work with does the deployment, and then they worry about the environment, infrastructure, and other things.

We do the deployment by ourselves because we need to test or develop some applications and do the PoC phase.

Docker is perfect for what I do, though it is really limited as a tool.

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