Docker Reviews

In our company, I have used Docker to launch an application publicly. The aforementioned application becomes available to end users via CloudFront. Docker is also used to cache the optimized performance.  

Docker hasn't been directly able to improve our organization's deployment processes. 

Docker offers a resilient system with minimal failure chances and optimized performance. For example, if an EC2 is utilized, the software container can be customized to allow only the specific benchmark of resources to be used. I found the solution to be easily customizable. 

The vendor should release a monitoring tool or include monitoring capabilities in Docker that can be used to monitor container performance and other Docker-based solutions. 

I have been using Docker for two years. 

I would rate the stability a nine out of ten. As containers are isolated and not dependent on each other, stability is satisfying in Docker. With the solution, when one service is down at the production end, it won't affect the functionality of other services running in parallel. The solution can be considered stable 99% of the time. 

I would rate the scalability an eight out of ten. Docker offers satisfying scalability features, and it depends upon the correct configuration being run within the virtual machines. Scalability in Docker is easier to manage than in legacy-based documents.

Presently, Docker is used by only me in our organization. Docker is an open-source solution. In our organization, we work with Docker on average once a week. At our company, we are not planning to increase the usage of Docker. 

Previously, applications were directly deployed in the server in our company instead of packaging the applications and running them on isolated environments. For instance, if any application experiences outage, it affects the other services as well, but with Docker this issue doesn't arise. 

I would rate the initial setup a ten out of ten. Docker offers an effortless setup process. As part of the setup, I have faced some configuration failure issues in Docker compose utility, but I was able to resolve it on my own with some changes in configuration. A feature of Docker can be made live in 20 to 30 seconds but the total deployment of the solution took me around one and a half days. 

As part of the deployment process, I inputted the code in the local environment and tested it on my personal computer using the Docker desktop utility. Following the aforementioned step, I pushed the code to the cloud and cloned it in EC2. Then, I developed a few necessary configuration files for Docker deployment and building.

As the last step of the deployment, the commands are run successfully to make the solution go live. Only one professional is enough to deploy Docker. To implement maintenance for a production-based cluster, a team of three professionals, one lead and two other team members, is needed. 

It's an open-source solution, so it doesn't cost anything. 

Docker is a trending tool and is being used for numerous production based applications, so instead of evaluating multiple tools, our company adopted Docker. 

I find Docker to be a user-friendly product. Docker acts as a stand-alone application without any dependency on other hardwares, so it can be used in an isolated environment. The tool can be easily customized. 

In our company, the product is running on EC2. I have restored all the required packages and need to compile the code within a container using the Docker tool. After the aforementioned step, Docker is used to run a few specific images where images are not dependent on each other. If one of the running images on Docker malfunctions, there won't be any cases of outage because the environment remains isolated. There is no interdependency between containers in Docker. 

Docker's container orchestration capabilities support our organization's projects with minimal downtime and low failure chances and offer a robust system. Our company has a Docker compose utility to customize the workflow and make it operate smoothly. Overall, I would rate the solution a nine out of ten. 

Currently, we are creating a JAR file and using microservices. There are around 178 services in a single project. We use Docker to manage and do load balancing for all the services together.

We are using Docker to host applications. We are using Docker Compose and sometimes Docker Screen.

We are facing multiple issues with the solution's stability.

We have been using Docker in the same project for five years, and we have recently deployed Docker into Kubernetes for four years.

We are facing multiple issues with the solution's stability. It is very difficult to analyze how much load a tool takes. Sometimes, our Docker images get crashed due to the unavailability of space.

I rate the solution a six or seven out of ten for stability.

Approximately, 400 users are using the solution in our organization.

I rate the solution a nine out of ten for scalability.

The solution’s initial setup is simple.

We implemented the solution through an in-house team. It took me around three to five hours to deploy the solution. Docker is easy to use and implement. For the deployment process, we used Docker in the CI/CD pipeline. Then, we pushed the Docker images to the Kubernetes as per the environment. We used Kubernetes to host and balance the load.

Since Docker is an open-source solution, it is free of cost.

Docker made it easy for us to monitor the microservices. Secondly, we were able to manage the key load balancer. Thirdly, we wanted to create a secure layer of protection for our organization. So, we started using the containers above the hypervisor.

It was like using a new operating system. We created our own network adapters. We created another isolated network inside the Docker containers to keep our organization and project safe and secure. We consider this very helpful in the secure software development life cycle.

We're implementing multiple stages in security. We are signing Docker images, Docker containers, Kubernetes containers, Kubernetes nodes, and clusters in cryptography. We are signing these so that no one tampers with the code or the docker images. We are doing this from a security point of view.

The solution's containerization helps us in providing integrity and availability. If you use a microservices architecture, I recommend implementing Docker and Kubernetes. I would recommend Docker and Kubernetes to manage multiple microservices running simultaneously.

We had to configure multiple services, like the utilization of the CPU and the utilization of the RAM for the service that we were building. Additionally, we had to mention the network adapters we will be using. We followed multiple benchmarks, like NIST Benchmarks and CIS benchmarks.

There were multiple advantages to using Docker. The most important advantage was scalability and availability. As I am working in the security team, I'm looking after the integrity of the Docker images.

Overall, I rate the solution an eight 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. 

Our company uses the solution for the production environment, web projects, and hosting services. For example, we use it to host an NGINX box manager with  proxy, reverse proxy, and DNS server. 

We host a bunch of web services for clients and deploy both on-premises and on the cloud. Several of our development teams use the solution.

I also use the solution in my home lab. 

The solution is easy to deploy for clients so it saves a lot of hassle. 

The networking is an impressive feature. 

The volumes for persistent storage could be more user friendly right out of the box. 

I would like an option to just use it as local storage or some kind of NSF or CIF. Or to mount the volume straight to a Google Drive or through a particular cloud storage.

It's not that these things are impossible, but you have to do some extra work or configurations. 

I have been using the solution for three years. 

We use the solution mostly with Linux and it is stable.

We would like better stability with Windows containers. We need to use some kind of IAS to host them so support for these legacy projects would be a tremendous help. 

The solution is definitely scalable.

The documentation and community are good. I've never had a problem that I was unable to fix with a little bit of Google research. The official documentation is all you need to figure things out. 

I did not previously use another solution. 

The initial setup is straightforward. 

I handled implementation by myself and it was an easy process. 

There is definitely an ROI because the open-source version is free. 

The solution offers an open-source version that is free and includes a lot of functionality. 

When using the solution, don't rush or you might get overwhelmed. It takes a little bit of time to figure out how things work. Basic networking knowledge will save a lot of time. 

I rate the solution a ten out of ten. 

Docker is a development platform for containerization.

The solution offers speed and flexibility.

The solution could offer better documentation.

I have been using Docker for more than a year. We are using the latest version of the solution.

I rate the solution's stability an eight or nine out of ten.

The solution is scalable.

The initial setup is straightforward.

I recommend the solution and tell them to explore it the first time and then make a decision. It's reliable, quite mature and reliable.

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

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.

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. 

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.