Docker Reviews

I use Docker for containerization.

Docker has helped my organization by allowing us to run microservers in our environment.

The most valuable feature of Docker is its portability, ease of security management, and low resource usage.

The runtime and security could improve in Docker. Security is paramount in the cloud and important.

I have been using Docker for approximately three years.

Docker is a reliable solution.

I rate the stability of Docker an eight out of ten.

The scalability of Docker is good. It is good for packaging applications.

I rate the support from Docker an eight out of ten.

The initial setup of Docker is straightforward. It is simple to receive the build and the file image you want.

I have seen a return on investment using Docker.

Docker is a free open-source solution.

My advice to others is to use only office images from reputable sites and keep in mind it does not run containers at the root.

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

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. 

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.

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. 

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.

Our primary use case is to build and bundle applications.

The most valuable feature is that it gives you the same environment as on a developer machine as well as a production machine relevant to specifications. The binaries and dependencies are all bundled together and they are in a similar fashion in both places.

I would like to see better management layers. One example of this would be binary shipping. I would also like to see Docker utilize a concept like Red Hat Family.

I have been using Docker for three to four years.

The stability is excellent. Sometimes, memory management can be tricky.

Docker is scalable on both community and commercial levels. I am using the community version. There are around one hundred to one hundred and twenty of us using Docker on a daily basis.

For customer support, we are using the documentation on the forums and they are suitable.

The initial setup was very simple and straightforward.

You can use either an in-house or vendor team. We simply downloaded Docker into our organizational environment.

There are a sufficient number of YouTube videos and best practices to build Docker. I would encourage a potential user to investigate those videos. On a scale of one to ten, I would rate Docker a nine.