Docker Reviews

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. 

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.

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.

Containerization is one of the use cases of Docker. Basically, Docker provides containers to its users. So, users can build, run and share containers among developers.

Feature-wise, Docker is very user-friendly. Also, though the solution may look basic, it is a very relevant one in the market owing to the functionalities that it provides to its users.

I'm not a developer but a salesperson, so I cannot contribute much in terms of what needs improvement in the solution from a technical perspective.

From a marketing perspective, we, as distributors, wish that Docker would figure out a way to reach more customers. Marketing of Docker is one area that needs to improve. So, since Docker was commercialized a year and a half ago, it should plan to work on its marketing part. Also, there is room for improvement in terms of the security provided by the solution. So, it should be an ongoing process that never ends.

I work in an IT company, and we are currently working on a distribution model. So, we are the distributors for Docker. Hence, we are not using Docker much and are involved in selling it. So, my company has been associated with Docker since the time it started its business.

It is very stable. So, the tool is as stable as it can get in terms of containers.

Regarding the solution's scalability, it can be automated, but Docker does not have that automation feature. So, its integration process can be carried out with an infrastructure automation tool like Terraform. In short, scalability is one of the features that Docker offers for anything with containers or anything you're running in containers.

Regarding our customers who are using Docker, I would say that we have a great and huge market share. Even though I feel that Docker's market share is around 90%, it could be more than that.

Docker provides all the technical support to its users, especially to those who purchased a Docker license, which comes with a basic SLA agreement. It means the technical support is covered directly by the vendor. Docker has a team of engineers who work in its technical support team serving globally 24/7.

The solution's initial setup process was straightforward. Basically, it is an open-source product, so one does not have to worry about the setup process since it's as basic as it can get. So, our company does not have to position the solution with the customers because they already use it. We just have to make sure the customers are shifted to the enterprise version of the solution so that our company can make some money.

The solution can be deployed on the cloud or on-premises, so our customers can choose a hybrid model.

Regarding the deployment process, one can directly download Docker from their official website, making it very straightforward. Also, I am unable to elaborate further since I have never personally deployed the solution as a salesperson.

Regarding the deployment and maintenance of the solution, any developer can deploy it. So, even you or I can try to deploy it since it is very straightforward.

Customers pay for the license through a yearly subscription model, where they pay per license. This means that the license is based on a subscription, and the customer pays annually for each license they use. If you consider the features that Docker provides to its users, I would say that the solution is affordable.

Docker is considered to be a flagship product when it comes to containerization. If a person is going to run containers for developers, Docker should probably be chosen. Docker's enterprise version is also a great solution. For any enterprise organization that is running containers or building or developing application containers, Docker will offer some great features that allow a person to collaborate with the whole development team and manage everything. Docker provides its users with the functionality to control and manage everything. Since Docker is the best solution in terms of containerization, I rate the overall solution a ten out of ten.

We used to have a silo problem. Docker solved it because we're able to containerize the microservices that we're developing in the form of Docker mail.

Once we run the Docker image, it becomes a container. This container is guaranteed to run in every machine because we're installing Docker as the platform. On top of Docker platform, we're curating the Docker images and running the container. That container has a limited number of libraries and a limited number of data, which is required to run the application.

Each container has a limited library system, which is required to run the application. This encapsulation makes it work perfectly, irrespective of the system. It works perfectly once we have encapsulated the application and containerized it. This is guaranteed to run in each machine.

We're deploying the solution on Azure cloud. We're curating the CI/CD pipeline. In the CI/CD pipeline, we're curating the Docker images and pushing it to the container registry. We're writing the steps for how to build the Docker image into the YAML code. Once the Docker image is built, it's pushed to the container registry. We're writing this YAML code in the pipeline.

Every person on the DevOps team is using this Docker tool.

We have plans to increase usage because it's a great tool, and it's the latest technology. We're no longer developing monolith architecture, so everyone is developing applications with microservices. Docker is the best tool to containerize the application and encapsulate it.

We used to work on monolithic architecture to develop the application until it goes to the production environment. It takes a huge amount of time. Now, we are using a microservices architecture. Rather than creating the application as a whole, we are dividing the application into small services. Each microservice is loosely coupled. With each microservice, we can develop and containerize it in the form of a Docker container.

If an application has a hundred microservices, like on an e-commerce portal website, then the login is usually one application, the catalog is one application, and the E-card is one application. Each application can be considered as one service. For each microservice, we can develop a code and containerize it.

Containerization is the most valuable feature. I can communicate to the Docker containers using other containers. The copying feature is helpful because if a container dies, we won't lose the data. That data is retained because of this data volume feature. We mount it to our shared system or any shared folder.

I would like to see a more UI-based tool so that students can easily understand it rather than memorizing all of the Docker commands. Some people try using Docker desktop and containers to make it graphical.

Docker Swarm could have more advanced features, like Kubernetes, which has an auto scaling feature and cell-filling capabilities.

I have used Docker for four years.

I would rate the stability as seven out of ten.

I would rate the scalability as seven out of ten.

I would rate technical support as seven out of ten.

Setup is simple. We can install Docker with just one command. It doesn't take more than three to four minutes to run the pipeline. A Docker image is built in that time frame.

We're running the pipeline in a self-hosted agent or Microsoft-hosted agent.

Docker Compose can be installed easily. It allows you to use multiple containers at a time. Docker Swarm can also be installed easily.

Docker is open source. To use a Docker enterprise model, we would need to pay for it.

I would rate this solution as seven out of ten.

My advice is to create an account on Docker Hub. In Docker Hub, there are three Docker images available for practice. We use GitHub to see how we're making the Docker images and then push it to the public Docker Hub. I have an account in Docker Hub and have images there that I can reuse later. I would also advise completing a Udemy course for Docker or watching YouTube videos about it. This will make Docker easier to understand.

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.

We use this solution for our web applications and websites for automatic deployment. We also have a cloud based solution that we sell as a product and we offer cloud hosting, which is Docker based. Our clients have access to a graphic user interface where they can deploy their websites with one click and we use Docker in the back end to make that possible. 

Docker is an entirely containerized cloud solution that supports different types of applications running on the cloud including websites, web applications, APIs and some Lambda functions. We have a whole bunch of stuff running on the cloud. We have thousands of users supported by this solution. 

There are ways of using Docker where you have absolutely no dependencies on the environment that you work in. This allows us to deploy Docker anywhere anytime and this has been most valuable.

Docker removes any dependancies when it comes to deployment. We can ship it between different devices and different locations without our clients being impacted or aware. In once instance, we redeployed a client's container without losing any of their data. 

There are elements of stability that are problematic. One of the most recent upgrades created a major incident on our cloud, whereby the containers were not restarting automatically. Docker is a fairly new application and has matured and improved since 2016 but still needs improvement on stability. 

Prior to using Docker, we used a CH root and jailing process. Essentially, Docker is a CH root on steroids combined with an image management system that is based out of git code. When you're dealing with such low level technology, there should not be issues with stability. 

We have been using this solution since 2016. 

This is a scalable solution

The setup on the most recent versions of Windows is pretty straightforward. The setup on Mac is also pretty straightforward, but there are networking problems.  Docker, it doesn't play well with the Mac virtual hypervisor. There are some issues on that side. On Linux, well, it's less straightforward, you have to know how to work it out. There are no performance or networking issues.

We have done in house deployments and we have also used other tools like Kubernetes or Docker Compose. We have our own PHP library that can deploy Docker containers, which is called Linux for Composer. It is oriented towards helping PHP developers to use Docker to make things more simple. 

We have definitely experienced ROI because it cuts down on development time. There are no surprises when it comes to deployment. It cuts down on development, deployment and it cuts down on staff. There are multiple advantages including on the financial side.

We've had a look at other possible solutions such as KVM and Pod Man. Pod Man is not very mature right now. There are a lot of things that we're used to being able to do with Docker that we can't do right now with Pod Man.

We're not excluding the possibility of using Pod Man. There is also an equivalent to Docker which is the Windows subsystem for Linux, WSL two. We've used that for a few projects in Windows environments, and we are considering putting our Linux distribution on WSL two.

I would advise others not to use Docker as a virtual machine or to think of it as being similar to VMware or Virtual Box. It has an entirely different use case. They have to think about it as a system that is used on an ad hoc basis. 

If you build thinking that it is temporary in nature, you will have the full benefits of Docker. 

I would rate this solution a nine out of ten.