Docker Reviews

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.

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. 

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.

I use Docker primarily for backend services to containerize applications or for API communications.

The most valuable feature is the simple containerization. I can specify what I need to install in a shell to ensure the application runs. It's a straightforward and easy-to-use feature. I also use it with CI/CD tools, finding it a good solution for integration.

In terms of communication between services, perhaps the configuration within networks between containers could be improved.

I have been working with Docker for about six years.

The stability is excellent. I would rate it ten out of ten.

By using Kubernetes, scalability is simple and can be done without issues.

Some developers might use virtualization solutions like VMware, however, Docker is much better because it is simple.

Overall, the setup is simple.

I consider Docker's pricing to be affordable.

Some developers might consider virtualization solutions like VMware.

I would recommend Docker for a wide range of users, from 50 to five million users, as it is simple to configure. 

I rate the overall solution ten 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 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.

I have an energy management platform running on AWS, but I saw some limitations in that setup. So I'm designing one to be independent and containerized rather than using AWS services. That is why I'm now checking if I could go to a Red Hat OpenShift or EKS.

The solution's most valuable feature is having containers independent of the operating system or environment. Also, you can just be modular and scale with the solution.

The solution’s documentation could improve a bit.

A new feature was added to Kubernetes to deploy and manage containers. Currently, it is a bit of a tedious process to combine containers using Docker. Hence, a new way to deploy containers would be a good feature to be included in Docker's next release.

I have been using Docker for one year.

It is a stable solution.

The solution is scalable.

I've never contacted Docker's technical support, but I contacted the developer of a few images that were incompatible with Mac.

The initial setup is fairly easy and fast.

The pricing of the solution is fairly cheap.

I am using the latest version of Docker. Currently, we have four people using Docker in our company. My company chose Docker because it is popular and used on all platforms.

People should definitely use Docker. Since there's a learning curve, users should first start small and then expand. It also depends on your use case. You need to understand what Docker is because it is not always the right solution for everything. Docker is very lightweight, and you can use it to build containers and create your application. It will be modular and cross-platform.

Overall, I rate Docker an eight out of ten because it is a cross-platform solution that is straightforward and easy to use.