Docker Reviews

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. 

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 the tool for some of our services. We use it for containerization.

Load balancing features are valuable. We are leveraging this software for containerized services. We are using EKS for orchestration. We are leveraging almost all features. The solution helps save costs. We can know how much CPU memory is required so we can manage it accordingly.

Docker management is very difficult when we have a large number of nodes.

I have been using the solution for the last two years.

I rate the tool’s stability a six or seven out of ten.

I rate the tool’s scalability a six out of ten. We have more than 500 users. The tool is used extensively. We have plans to increase usage in the future.

We get good support from AWS.

The setup is straightforward. We need ten people for deployment, including managers, developers, and the IT team.

We can deploy the product ourselves.

We use the open-source version.

We use EKS for large applications. I will recommend the solution to others. If people want to leverage load balancing and containerized services with less CPU and load management, they can use Docker. We must pay for EKS based on the clusters and nodes we use. The price depends on the use case. Overall, I rate the solution 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.

Docker allows you to run multiple virtual machines independently. 

The solution is not easy to manage and it is one of the reasons why people introduce orchestration tools to manage it. 

I have been using the solution for six to seven years. 

The tool's stability is high and I would rate it a ten out of ten. 

We use the solution 24/7. 

The tool is an open-source product and there is no technical support for it. 

We use Hyper-V and VMware as per our client's requirements. 

The tool's setup is difficult and I would rate it a two out of ten. The tool's POC can be completed in a couple of hours. However, if the project is big, then deployment can take around one to two months to complete. 

The solution is an open-source technology and not a commercial product. However, you will have to pay sometimes. The tool's pricing depends on the vendor. 

I would rate the product a nine out of ten. The solution is a virtualization technology that is more like a mini-computer. 

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

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. 

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.

I am able to containerize my application using Docker on my Docker account.

Deploying two solutions is much faster and easier for me on Docker. Docker makes deployment much simpler and more efficient.

The deployment is quite fast, which is beneficial.

I think Docker has done an excellent job on their website in illustrating the installation process and addressing any challenges that may arise. 

Their website provides clear instructions for deploying Docker on various operating systems, including Mac, Linux, and Windows environments.

There is always room for improvement.

I often refer to forums such as StackOverflow to learn from other developers' experiences and the challenges they have faced while using Docker.

I have been using Docker for the last two years.

We are using the most recent version. I released the most recent update two or three days ago.

I prefer not to disclose that specific project at the moment because it is a personal one and not related to LiveScale.

I would rate the stability a nine out of ten.

I am the only user.

I have used Apache Web Server.

The initial setup is straightforward.

It can be deployed in less than thirty minutes.

I was able to deploy it myself.

Regarding my last deployment, I used Docker as a containerization platform to package and deploy my application. As for the design, I purchased the Blue on the Bureau theme for $250 and used it on my Mac computer.

I found the deployment process to be quite straightforward.

It is installed on-premises on my local machine. However, whenever I need to make updates or changes, I push them to Git to maintain a version control account.

I prefer to pay on a monthly basis.

The pricing is reasonable. 

Pricing is based on the number of users.

Based on my experience with Docker and the speed and ease of deployment it offers for various applications, I would highly recommend it to others.

I would rate Docker, a nine out of ten.